> When I sorted out the multithreading issues we were having
> with FLTK, I believed that MY_LockableOutput was no longer
> needed, and all instances of it could be replaced with
> Fl_Output. What I didn't realize is that the class
> MY_LockableOutput also has another important method:
> int MY_LockableOutput::handle(int) { return 0; }
> which I'm told will permit arrow key presses to propagate to
> the menu. So restoring that approach is my next task.
That seems like a bit of a sledgehammer to me - if you just use a
standard Fl_Output, you can make it shrug-off the keyboard navigation
focus just by setting
output->clear_visible_focus();
Or perhaps
output->visible_focus(0);
Which I think is analogous.
If you don't want keyboard navigation at all, I think you can disable it
globally, maybe something like;
Fl::visible_focus(0);
Would probably do it.
--
Ian
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
