Re: frequent polling in LyX (plus LyX under DRT screenshots)
On Mon, Sep 02, 2002 at 09:48:22AM +1000, Amir Michail wrote: > You can see some preliminary results here in the following screenshots: > > http://www.cse.unsw.edu.au/~amichail/lyx8.png Nice ! > BTW, could someone tell me if the functions shown in the pictures > are particularly relevant to the action? The darker the action label, > the more relevant it is perceived to be to the action shown in the > before/after pictures. Looks good, I think. > I also found another problem with getting rid of cursor blinking. > If you type a sentence and press return, the cursor will not appear > for a while until it is told to blink on. By then, the after picture > has already been taken, so cursor tracking is broken. So it's not sufficient > to disable blinking. We also need to make cursors appear immediately when > they are moved in various contexts. It would be really nice if out of this work somebody fixed our horrendously broken cursor handling :) john -- "Take the ideas you find useful. Try not to get hung up on the labels." - Jonathan S. Shapiro
Re: frequent polling in LyX (plus LyX under DRT screenshots)
Amir Michail wrote: > I also found another problem with getting rid of cursor blinking. > If you type a sentence and press return, the cursor will not appear > for a while until it is told to blink on. By then, the after picture > has already been taken, so cursor tracking is broken. So it's not sufficient > to disable blinking. We also need to make cursors appear immediately when > they are moved in various contexts. The cursor handling is a bit broken. We _always_ should hide *and* show the cursor, but sometimes we just "forget" to show it as it really should show as then we get cursor trails :(. IMO we need some sort of counter or some sort of flag (as the undo does) in which we see if the cursor is already hidden and don't do it again. So the first one hiding it is responsible for showing it again. When we changed this behaviour it should be quite easy tracking down where we "forgot" to put a showCursor call. Jug -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Mitterstrich 151/A Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39050 SteineggWeb: http://www.lyx.org/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
Re: frequent polling in LyX (plus LyX under DRT screenshots)
Hi, Perhaps a configure flag could be used to build LyX in a way that works well under DRT? Although the polling change I mentioned (and others) may not be bug free, they do seem to get LyX working under DRT. You can see some preliminary results here in the following screenshots: http://www.cse.unsw.edu.au/~amichail/lyx8.png >From the function sequence in the picture above, we see that the user probably moved the cursor up. However, that's not the whole story as made obvious by the before/after screenshots. In fact, the cursor moved out from math mode as well. This shows the importance of before/after pictures in explaining past actions (possibly performed by others). BTW, could someone tell me if the functions shown in the pictures are particularly relevant to the action? The darker the action label, the more relevant it is perceived to be to the action shown in the before/after pictures. To see how we arrived at the previous screenshot, see the following: http://www.cse.unsw.edu.au/~amichail/lyx1.png http://www.cse.unsw.edu.au/~amichail/lyx2.png http://www.cse.unsw.edu.au/~amichail/lyx3.png http://www.cse.unsw.edu.au/~amichail/lyx4.png http://www.cse.unsw.edu.au/~amichail/lyx5.png http://www.cse.unsw.edu.au/~amichail/lyx6.png http://www.cse.unsw.edu.au/~amichail/lyx7.png http://www.cse.unsw.edu.au/~amichail/lyx8.png I also found another problem with getting rid of cursor blinking. If you type a sentence and press return, the cursor will not appear for a while until it is told to blink on. By then, the after picture has already been taken, so cursor tracking is broken. So it's not sufficient to disable blinking. We also need to make cursors appear immediately when they are moved in various contexts. Amir
