Automatic key view handling
Automatic key view handling
- Subject: Automatic key view handling
- From: Ricky Sharp <email@hidden>
- Date: Mon, 21 Feb 2005 08:09:06 -0600
I spoke a bit too soon in my previous message (entitled "Overlapping views no more") regarding the automatic handling of key views.
I'm able to reproduce the problem with full keyboard access on or off.
Take as an example, the following setup:
+----------+
| [ edit field ] | <-- tabless tab view: first tab has edit field; second contains non-keyable item
+----------+
(*) First Tab
( ) Second Tab
[ edit field two ]
I wired things in IB such that the next key view loop is:
Tabless tab view, NSMatrix (radio group), edit field two
For the most part, everything works well. However, If the key view is the first edit field (the one inside the tab view) and I then click on the "Second Tab" radio button, no key view is re-established. This is because the the second tab doesn't contain any item that can accept the key view. Pressing the tab key (or clicking in edit field two) will set the focus there.
What I could do is that whenever my tab view changes, I can somehow sense that no view currently has first responder status (my guess is that firstResponder will return nil. I can then call [myTablessTabView nextValidKeyView] to find the view (if any) that should now have first responder status.
Shouldn't the framework do this for me automatically? If this is a bug/limitation, I can write up a report.
--
Rick Sharp
Instant Interactive(tm)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden