[interfacekit] Re: Helping out

Christof Lutteroth wrote (2007-08-07, 17:42:16 [+0200]):
> Axel Dörfler wrote:
> >> I thought the focus _is_ the keyboard input, no?
> > 
> > In theory, yes, in practise, not exactly :-)
> > When a menu pops up, no hooks are called on the window either, and no 
> > visual effect would tell you that this menu is in fact another window 
> > that steals something from it's "parent".
> > It is not aware that it lost the keyboard input.
> > 
> > I think the correct way in the app_server might be to have that 
> > mechanism of a parent window that has focus, but redirects all input to 
> > its top-most open menu window. Currently, it's system-wide, which is 
> > apparently not a good choice :-)
> 
> That makes sense.
> 
> So is there any task you think I could work on as a Haiku newbie? 
> Probably not the menus since this seems to require more knowledge about 
> the BeOS than I have.

Actually, trying to fix an interface kit bug was not such a bad idea. You 
just happened to pick the wrong one... :-)

Don't try to pick the buggy "selected text drawing" either.

Maybe look at another bug in the interface kit. Perhaps the BListView still 
has some? But maybe not this "listview in tabview" bug. That appears to be 
another app_server bug (or more likely a BView state saving when it is 
detached bug).

You could always try to look into font sensitivity issues. That's a good 
way to get to know the interface kit API in more detail.

Best regards,
-Stephan

Other related posts: