> Albrecht Schlosser wrote:
> > On 12.10.2010, at 18:28, Greg Ercolano wrote:
>
> >>     Currently the docs for Fl_Button (under 'Description') says this:
> >>
> >> Buttons can also generate callbacks in response to FL_SHORTCUT events.
> >> The button can either have an explicit shortcut() value
> >> *or a letter shortcut can be indicated in the label() with an '&' 
> >> character*
> >> before it. For the label shortcut *it does not matter if Alt is held down,*
> >> but *if you have an input field in the same window*, the user will have to
> >> *hold down the Alt key* so that the input field does not eat the event 
> >> first
> >> as an FL_KEYBOARD event.
> >>
> >>    I don't think we currently hold to that last sentence, as it seems
> >>    if there's an input field in the same interface, still regular
> >>    letter buttons will trigger the shortcuts.
> >
> > You're right if you read the text literally - however, I think that it meant
> > something like
> >
> >    "... but *if you have an input field in the same window*"
> >
> > add here:
> >
> >    "... that has the focus".
> >
> > If we add this little omission, then the text and its intention becomes 
> > clear:
> > Label shortcuts can be triggered no matter what additional modifiers are 
> > pressed
> > or not, as opposed to explicit shortcuts. This doesn't say anything about 
> > menu
> > bars though, but that's IMHO a special case.
>
>       I see. Interesting, and quite possibly true.
>
>       My personal opinion on this, current docs aside:
>
>               * In my mind the little underbar that appears under a label to 
> indicate
>                 a shortcut should give a consistent visual cue to the user.
>
>                 If it means 'Alt' is needed (or in the case of Macs, 
> 'Cloverleaf'),
>                 then it seems to me it should be consistent for both buttons 
> and menus.
>
Consistent requirement of use of a modifier key is not possible
because submenus can be triggered by a single letter shortcut.
I thus suggest not to change the present behavior and to just
clarify the doc as suggested by Albrecht.
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to