[BUG?] initialFirstResponder killed by Panther?
[BUG?] initialFirstResponder killed by Panther?
- Subject: [BUG?] initialFirstResponder killed by Panther?
- From: Stephane Sudre <email@hidden>
- Date: Thu, 4 Mar 2004 15:18:52 +0100
Can someone remind me how the initialFirstResponder is supposed to work
in Mac OS X?
I have a NSWindow which is displayed by a runModalForWindow: message:
Inside this NSWindow, there are 4 views:
2 TextFields A & B
1 PopupButton
1 TextView
The nextKeyView chain is set like this:
TextField A -> TextField B -> TextView -> TextField A
The initialFirstResponder of the NSWindow is set to be TextField A.
In Mac OS X 10.2.8, when I display the dialog and tab to TextView (so
TextView has the keyboard focus), validate the dialog and then
redisplay the dialog, the keyboard focus is set to "TextField A" =>
This is correct.
In Panther (10.3.2 Client and Server), when I follow the same
procedure, the keyboard focus is set to "TextView" => This is incorrect.
(i) Is this new behavior introduced to conform to the documentation for
setInitialFirstResponder:?
(ii) If the answer is YES, why not put the initialFirstResponder
feature to the trash completely? IMHO, when you display a NSWindow via
the Sheet or Dialog APIs, it's as if the window is displayed for the
first time.
(iii) No information on this modification in the Cocoa release notes,
does it mean it's a bug introduced in 10.3?
--
Stephane
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.