Re: is the nextKeyView really used by Cocoa ?
Re: is the nextKeyView really used by Cocoa ?
- Subject: Re: is the nextKeyView really used by Cocoa ?
- From: Jean-François Veillette <email@hidden>
- Date: Wed, 11 Jul 2001 08:09:50 -0400
the window's initialFirstResponder had to be set, and part of the chain.
Try to set it to your NSTextField1.
- jfv
Le Mercredi 11 juillet 2001, ` 06:06, Stiphane Sudre a icrit :
To try that one:
launch IB
Create an attention panel
Empty the window
Add 3 NSTextFields
+------------------+
| NSTextField 1 |
+------------------+
+------------------+
| NSTextField 2 |
+------------------+
+------------------+
| NSTextField 3 |
+------------------+
Set NSTextField 3 to be the nextKeyView of NSTextField 1
Set NSTextField 2 to be the nextKeyView of NSTextField 3
Set NSTextField 1 to be the nextKeyView of NSTextField 2
So my guess is that when I run this and do a tab from NSTextField 1 I
will go on NSTextField 3.
Guess what ? I don't. I go on NSTextField 2.
Cool. So I looked in the Learn Cocoa Book to see if I was not a
complete moron by thinking that nextKeyView doesn't mean what it means.
Happily for me, it means what it means by all mean.
I also tried in the code with setNextKeyView. Same result.
I don't even speak of adding a NSTableView in this and the fact that
the NStableView gest involved in the nextKeyView loop.
It's not even using the depth hierarchy. Then nextKeyView mechanism
seems to be completely screwed.
Mac OS X 10.0.4.
I checked that one a lot because it's so Huge that I still think I'm
wrong.
_______________________________________________
cocoa-dev mailing list
email@hidden
http://www.lists.apple.com/mailman/listinfo/cocoa-dev