Matthias Melcher wrote:
> On 23.02.2011, at 21:22, corvid wrote:
>
>> I wrote:
>>> If the widget flag enum says:
>>>
>>> INVISIBLE = 1<<1, ///< the widget is not drawn but can
>>> receive events
>>>
>>> then why is visibility required in:
>>>
>>> unsigned int takesevents() const {
>>> return !output() && active_r() && visible_r();
>>> }
>
> Normal widgets will not receive shortcut events when hidden,
> or any of their parents is hidden. There are a few events
> that still go through though, HIDE, SHOW, ACTIVATE, DEACTIVATE..
>
> Shortcut events will ultimately be sent to a custom handler.
> See: void Fl::add_handler(Fl_Event_Handler ha); and void Fl_Menu_::global();
So it sounds like the docs aren't wrong,
since 'some' events can make it through, but not ones that
involve calling takesevents().
If that's the case, then perhaps STR#2574 isn't needed
<http://www.fltk.org/str.php?L2574>
unless there's some doc strengthening that you think would help.
_______________________________________________
fltk mailing list
fltk@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk
