DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L1983 Version: 1.3-feature The documentation in events.html#events claims this: FLTK follows very simple and unchangeable rules for sending events. However, the rules for sending events are actually quite complicated, and not exactly unchangeable. While they are presumably documented somewhere in the docs, they aren't documented right there in the event delivery system. Here is matthiasm's description: """ Nope, the widget that has the focus gets the keyboard event first, then all its parents. If that didn't work, the keystroke is sent again as a SHORTCUT, but this time to the widget under the mouse pointer, then all its parents, then all shortcut handlers. """ In addition to that, there is the handler list which handles the event last. Also, when sending the SHORTCUT, I believe there is some hackery which tries to find the *closest* widget to the mouseover widget, in an undocumented way. The documentation should mention the complete event deliver scheme. ... and it would make me happy if it would remove the "very simple" part :) Link: http://www.fltk.org/str.php?L1983 Version: 1.3-feature _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
