Re: Master-Detail interfaces, Multiple Documents, and floating windows
Re: Master-Detail interfaces, Multiple Documents, and floating windows
- Subject: Re: Master-Detail interfaces, Multiple Documents, and floating windows
- From: Ron Aldrich <email@hidden>
- Date: Fri, 15 Sep 2006 15:58:25 -0700
On Sep 9, 2006, at 8:50 PM, George Orthwein wrote:
Not sure exactly why what you have isn't working but typically
inspectors bind via Shared App ->
mainWindow.windowController.document.xxx.
e.g:
Bind To: Shared Application
Controller Key:
Model Key Path:
mainWindow.windowController.document.transformationController.selectio
nIndexes
This is mentioned once in the docs but not in an obvious place.
Bottom of:
http://developer.apple.com/documentation/Cocoa/Conceptual/
CocoaBindings/Concepts/CntrlSelection.html
On Sep 8, 2006, at 6:17 PM, Ron Aldrich wrote:
In both cases, the Controller Key field is disabled within
Interface Builder.
I think that field is only used when binding to an
NSObjectController or its subclasses. It's really just a
convenience and when you "close" the binding you see a larger key
path is formed anyway, e.g. "selection.xxx.xxx". It just shows the
valid keys for a controller and thus requires that you use one of
them as the first part of the key path. That's my read of it anyway.
Hope that works for you!
George
Thanks, George - that's got the bindings working.
Now, I've run into another problem - my inspector becomes the main
window when it is clicked, and loses track of the selection - How
does one keep an inspector from becoming the main window? (Keeping
in mind that it has editable text fields).
Ron
_______________________________________________
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