dirac wrote:
> [...]
> if you add another widget outside MyButtonGroup, let's say
> a basic Fl_Button, then you click on it: MyButtonGroup loses focus and
> this is correct. Now if you push one of the three keys, the first time is
> spent to regain focus on MyButtonGroup, skipping the "pushed" state (as
> you can see from fprintf messages). Is there a way to make the grouped
> buttons always reactive apart from their focus?
Mmm, I think the only way in that case would be to have a global
event handler that processes the keystrokes, similar to the
keyboard.cxx test program which uses an Fl::wait() event loop
(instead of Fl::run()) to watch for keystrokes and process them.
In that case you could avoid most if not all of the handle()
method in MyButtonGroup, and just have the global event loop
send keypresses directly to a MyButtonGroup method that processes
it and triggers the right buttons.
Offhand that's all I can think of.. others might have more ides.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
