My current project is built around a master-detail style interface: the primary record owns the window content, while subviews display related content from various sources. My problem is that the tableViews which display these subordinate lists seem to mess up the responder chain's sequence for advancing the focus when the user tries to tab through page. What I would like to accomplish is to have the user be able to tab through top-to-bottom without noticing there are additional components in the page, as if it were one seamless document instead of (in this case) four. Further complicating this a little (I suspect) is that the m-d form is not shown in the window when the application launches, but replaces a window subview when called for, necessitating that the responder chain sequence be established on-the-fly, at runtime.
My first higher-level question then is how I ought to be going about establishing the tab-key behaviour sequence I want to achieve? My thought at the moment is to work out the list of controls I mean to have in order, then create outlets for them in the windowController, and as the master-detail view is added to the window, set the responder chain sequence in code. With the three subviews in this case, tabbing into and out of them in turn leaves me with six junction points with the main view. Tedious perhaps but manageable. Clearly this would not scale well as a solution, which makes me think there must be a better way to build a bridge than with matchsticks. Any guidance appreciated. ~ Erik _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
