While sometimes you simply have no choice but to loop through your
windows, it isn't the first approach that comes to mind for this.
In the MVC design, you have separate views (one in each document) and
separate controllers (each one referenced from each document 1:1) but
what you do need i
On Sep 27, 2009, at 11:19 AM, jon wrote:
the question it appears to me is: that this "treeController" also
is made into multiple instances with each new Document, is there
an already defined "loop" of these? (a list of the open document's
NSTreeController *treeController;)
No. I thin
ok, after thinking and analyzing what was going on, everytime i make
a new document in the running app, it created a new instance of the
window and all related stuff in the window including myOutlineView.
and then my dataSource in code remained the same that fills out these
outline vie
On Sep 27, 2009, at 7:04 AM, jon wrote:
so far i can find the chain of windows, like this, but i can't
figure out how to go deeper into them to be able to udpate the
custom view down deep maybe i'm approaching it wrong too...
The best way to do this is to use NSNotification. Post a
I am probably not describing it accurately,I'll try to understand
and describe what is going on more accurately in a bit, more likely,
i have one set of data, and each time a new window is open, it is
creating another instance of the outline view, i have not found away
to get at
On 28/09/2009, at 12:04 AM, jon wrote:
i have one instance of Outline View called myOutlineView, so no
matter how many documents are displayed on the screen, there is
only one myOutlineView instance,
I'm pretty sure that is never going to work. If I read you correctly,
you have a s
I've got a Document type program,
the windows are structured like this:
Window -> ContentView -> SplitView -> two CustomViews -> one of them
is Bordered Scroll view (outlineView) ->Outline View
i have one instance of Outline View called myOutlineView, so no
matter how many documents are
