matthiasm wrote: > > Sure, this is a compromise, but it works well in most cases. And one can > still override this feature by creating a new group class.
I see your point: this double-loop first tries to send an event to the widget where cursor is inside and if it fails it tries to send it to the neighbors, so that the local handling has a priority. This sounds reasonable but can be little tricky if the grouping structure is more complicated as it depends on the order which non-inside widget which one actually will get the event first. This may collide with the "natural" order of the widgets as they would be usually ordered to allow users intuitive tab-key navigation for focus. Anyway I agree that this implementation is good enough, maybe in the documentation we can distinguish which events never propagate to the widgets if the cursor is not inside so that users know in what circumstances they do not need to write a redundant Fl::event_inside() testing. Thanks a lot, Roman _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
