>
> See "Focus Events" and "Keyboard Events" on this page:
> http://fltk.org/documentation.php/doc-1.1/events.html#events
And, as a side note: The "dirty hack" might be to turn off keyboard
navigation altogether.
You can do this on a per-widget basis by calling
mywidget->clear_visible_focus();
"Disables keyboard focus navigation with this widget; normally, all
widgets participate in keyboard focus navigation."
And I think that calling
Fl::visible_focus(0);
Might do it globally. I think... Anyway, the idea would be that if
*nobody* consumes the keypress for keyboard navigation, then it will
find its way to the menu shortcut and be processed as you want.
That said, tweaking your subclassed GL window to take the focus and
consume the keypress itself is probably the better solution.
SELEX Sensors and Airborne Systems Limited
Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14
3EL
A company registered in England & Wales. Company no. 02426132
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
