Re: Entry / TextBuffer that does not listen to accelerators?

["muppet" <scott asofyet org>]

Jan Hudec said:
> On Fri, Sep 30, 2005 at 11:04:54 -0400, muppet wrote:
>> Which means that window-wide mnemonics and accelerators take precedence
>> over per-widget keystrokes.  And, if you think about it, it *has* to
>> work that way, or something like a TextView would eat all of the keys
>> that are supposed to be menu accelerators.
>
> No, it does not. I would even call it a bug. The event signal returns
> a boolean, whether it handled the keypress or not.

Well, it made sense at the time i'd figured out what it was doing.  :-/

At this point, it's way too late to be fixed in gtk+ 2.x.  Perhaps propose a
better solution to gtk-devel list for 3.0?


> By the way, how does it handle the tab switching? If you have an entry in the
> tab order, you can tab into it, but you can't tab out, as the tab gets
> inserted. That means that the container handles the tab only if it's child
> did not. Or does the child handle it? That would sound mad.

It's complicated.  I've poked through it in the past and decided not to go back.

-- 
muppet <scott at asofyet dot org>