dirac wrote:
> [...]
> Hi Greg, thank you for your helpfulness! Checking button::value() for
> both event and drawing routines is a good idea.
> Today I've tested your code and it works very well but I've found a
> little glitch 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?
Just add
case FL_SHORTCUT: // unused key pushed
before or after
case FL_KEYDOWN: // keyboard key pushed
case FL_KEYUP: // keyboard key released
and handle it like FL_KEYDOWN in the
following code.
This ought to do it - at least I would think so...
Albrecht
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
