>
> It appears that when grab() is on normal keyboard navigation
> is off. Is this the case, or am I doing something wrong?
I don't know - I guess grab() eats all the keyboard input, including
navigation options?
Still, if the intended use of grab() is for pop-up menus, I guess you
would expect navigation within the pop-up to still work...
OK, I just ran your example - for me, I can cursor and/or tab between
the three buttons - so it looks as if keyboard navigation *is* still
working. What is it that you are seeing?
> win.show(); // sidebar: how come putting this
> // below causes crash?
> if(argc > 1) {
> Fl::grab(&win);
> }
> // win.show();
I'd hazard that this is a problem because your window has never been
shown at all (if called the other way) so probably doesn't really exist
yet...
The grab() docs say "The window does not have to be shown()" but I think
it maybe has to have been shown at some point for the grab to work OK.
Or maybe not...?
Also, the docs say "under both X and WIN32 some window must be mapped
because the system interface needs a window id" which I guess would
certainly apply in your case, since there is only the one window?
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
