|
Hi DiapDealer,
The dataChanged() is fine as is. It will help reduce the number of times signals are flying around.
I have played with things a bit more and the amount of text in the clipboard when Sigil is started has no impact. It is just that there is something in clipboard at all no matter how small (such as the single letter "I"). That means that none of our syntax highlighting or anything else is related to the bug as these stayed the same across the two different cases (starting Sigil with something on the clipboard vs starting Sigil without something on the clipboard).
My guess the problem is something to do with the protocol of how Qt communicates with the X11 xcb clipboard. If there is something in the clipboard, some communication with the X11 windowing system seems to be timing out all of the time slowing all text selection down immensely. If there is nothing in the clipboard, then this problem never happens for the entire session.
Then there is the fact this is entirely a Linux issue and can not be seen on Windows or Mac points toward a Qt bug as well.
Is there an easy way on Linux mint to fire up a Motif based Window Manager and then fire up Sigil to see if the problem goes away or not. If it stays, that would probably rule out my INCR theory. Calibre via PYQT could be using a native python interface to the clipboard for all I know. This one really has me stumped. Adding a single letter "I" to the system clipboard before starting up Sigil has no effect on any other platform but Linux.
This is a real puzzler?
KevinH
|