imacarthur wrote: > The thing I still don't understand is whether we really need the > TrackMouseEvent() mechanism or not, given that it seems problematic here... > I don't really get what it does (since builds without it seem to > function)
I think that the (only?) point is to get FL_LEAVE events when the mouse pointer leaves the window. Someone might use this to disable highlighting of a button or something else. I don't think that this was intended to be used for embedded (GL) windows, but for the main window itself (and maybe that's the reason why it doesn't work in our case). When the mouse leaves the (main) window, FLTK doesn't get any more mouse events, and thus the application can't know that the mouse is outside of the window. With TrackMouseEvent() you do always get a FL_LEAVE event. > and if it generates floods of enter/leave events on a mouse > move... well that just seems like a Bad Thing... It wouldn't do that if it worked as expected ;-) And it doesn't do that with my (test) patch any more. > Do we need it? How does it help us? I don't know if we really need it. IMHO, the main question should be: is there an equivalent function for other platforms, or is this a Windows only thing? I didn't check the other platform specific files yet. If it's Windows only, then maybe it would be best to drop it. Maybe. If other platforms have an equivalent function, then Windows should have it as well. But maybe it's only an experimental thing like WSA_ASYNC_SELECT? Does anybody know more about it? Albrecht _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
