After doing more research the lack of event processing might be due to it not being the active window. I assumed events it received would still be processed but maybe not.
So, would I expect that if I create buttons that don't have restrictions in highlighting, etc., while not activated, just overloading the handle() function that this should work? Thanks > I am capturing mouse events and need to send them to my fltk application. > Since the fltk appl. is not the active application I need to use SendMessage > vs. SendInput. > > When I send MOUSEMOVE events, I do get a redraw but the fltk appl. does not > do things like highlight buttons, etc. I assumed that the window containing > widgets would loop through widgets and see if there is one that requires the > event (hence its over the widget). It obviously gets the MOUSEMOVE but when > the mouse is over buttons, the window doesn't seem to pass them to the widget. > > To get around the problem I'm planning on sending my own events and bypassing > the event system but this seems a waste. > > The coords I send are screen coords. So the order is: > > 1) Get screen coords of original appl. > 2) translate those screen coords to coords of fltk appl. > 3) do a SendMessage(windowHwd, WM_MOUSEMOVE, 0, lParam) where lParam contains > x and y coords. (x being the loword) windowHwd is the handle to the fltk > window that manages the widgets. > > I've read some of the mouse processing logic in run.cxx. Maybe I'm missing > something with regards to coords or the way events propagate to widgets. > > Thanks, > Bruce _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
