On Fri, Nov 21, 2003 at 08:36:53AM +0000, Angus Leeming wrote: > > You missed out *why* the core needs such fake move events. I > > understand the answer, but I do not know the question. "42" isn't > > good enoough for me :) > > The primary example is "select some text with the mouse and, with the > mouse button still pressed, move the cursor beneath the LyX screen".
Ah OK. Yes, this is fine, it's been a bug with the qt frontend for a while. We can certainly do this but i'd rather have a separate event stillWantScroll or whatever. Also, for maximum usefulness, the amount scrolled shoould be proportional to the distance that the pointer is away from the bottom or top of the screen. > More generally, selecting text with the mouse, even with the cursor > still in the LyX window, is a right, royal pain in the arse. > 2. If the timer is running the discard events passed to QContentPane's > MouseMove slot. This should make 'normal' selection much more > controllable. Perhaps, yeah. I suppose it would do. But I still think we need the separate event for the case above regards john -- Khendon's Law: If the same point is made twice by the same person, the thread is over.
