Stephen J. Turnbull wrote:
Greg Klanderman writes:
> that seems like it will not be an easy to make work or an improvement
> in code quality; you'll be getting y-positions relative to each motion
> event's window, which will not necessarily be the same as the original
> mouse button event's window, or even the same from motion event to
> motion event.
Is that really a problem, given that there are unlikely to be any
other windows near the modeline?
Well, there's the window immediately below the one whose modeline is
being dragged. If the code is able to move the modeline quickly enough,
the mouse won't end up over that other window, but relying on that in
the modeline code is going to make for brittle code. If you
click-and-hold over the modeline, then jerk the mouse down, it shouldn't
be hard to get the mouse over that other window. And I suppose that if
you have multiple small windows (a few lines each), you could even end
up with the mouse over a window that isn't even adjacent to the original
one. Bleah.
mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta