On Tue, Jun 3, 2008 at 8:20 PM, Gordon Apple <[EMAIL PROTECTED]> wrote:
>I guess I don't know hw to use that. The particular situation was a nib
> that is document related, but loaded and opened later by menu.
Ah, okay. But the solution is essentially the same: set up the
observers when you'
OK, if I understand the documentation correctly, the first suggestion
might work. Thanks.
I don't think the second one is applicable here. (I have used that
successfully within one class.)
Yes, the observed editLayer in displayController was being observed by
the displayEditcontroll
I have traced the problem to KVO race conditions.
In most cases these can be solved by setting up the key dependencies
and occasionally by using the NSKeyValueObservingOptionInitial
(Leopard only) option.
From your summary, I'm assuming that the editLayer property is
dependent on the NSI
(Sorry about that. For got to chance the Subject. -- GA)
I guess I don't know hw to use that. The particular situation was a nib
that is document related, but loaded and opened later by menu.
> On Tue, Jun 3, 2008 at 5:53 PM, Gordon Apple <[EMAIL PROTECTED]> wrote:
>
>> Both observations
On Tue, Jun 3, 2008 at 5:53 PM, Gordon Apple <[EMAIL PROTECTED]> wrote:
> Both observations are set up in the same Nib
> in "awakeFromNib".
If you have dependencies between objects in your nib, you can use
-[NSApplication applicationWillFinishLaunching:] to set things up.
Hamish
