Re: NSBrowser modifications ?

[mirko . viviani]

You wrote:

> > Add the alphanumerical keys in NSMatrix. 
> 
> Ahm - hm - while I would heartily agree on pageUp/pageDown, I wouldn't add
> alphanumerical keys at all.
> 
> Because if an application doesn't want them, then it needs to subclass
> NSMatrix, catch all key down events, and discard the ones it doesn't want
> and then call super's implementation.  This is very ugly.

Yes, you are right... and add it as a gnustep extension ?
It's disabled by default but you can enable it by calling a switch/method.

> > The pageUp/Down stuff could go in NSBrowser since the matrix is not 
> > the best place. (specially for matrix with multiple columns)
> 
> Just a quick thought - might be stupid - but I wonder whether it shouldn't
> go into NSView instead.
> 
> In NSView, we could check whether there is an enclosing scrollview, and in
> that case, scroll the enclosing scrollview.

Sounds nice.

> In the browser I suppose you would then pass the key down to the matrix,
> which would pass to superview, which sooner or later would be NSView and
> which would scroll the enclosing scrollview.

In the browser (or matrix) it has to be reimplemented since it should move the
dotted outline in the previous/next page. (IMHO)

--
Bye,
  Mirko