Re: Object Scope
Re: Object Scope
- Subject: Re: Object Scope
- From: Aaron Wallis <email@hidden>
- Date: Thu, 10 May 2007 07:09:58 +1000
Hey I.S.
Sorry for the lay terminology, I am still pretty new to all this :P
But you're on the money in your diagnosis! Thats pretty much exactly
what happens.
I've come across this "gotcha" a few times now and don't really
understand how to get around it.
On 10/05/2007, at 7:01 AM, I. Savant wrote:
On 5/9/07, Aaron Wallis <email@hidden> wrote:
I've got a class which is loaded when the Principal Class is
initiated, however the class also has a NSView and several out
IBoutlets/actions bound to it and I always seem to get an issue where
the instance that was created through initiator is in a different
scope to the *mystery* one that is created for the interface...
Okay, first suggestion: Go back over the documentation and review
the terminology. Your description is incredibly confusing and
apparently incomplete.
Second suggestion: It appears overall you're simply suffering a
typical cocoa "gotcha". I believe you have your class instantiated in
your nib (one instance) and are trying to create another in your code
at runtime (a second instance) and are confusing the two. If you've
instantiated your class in your nib, that particular instance != a new
one you create somewhere else.
If you're sure the above isn't the issue and / or you feel I've
misunderstood you, you're going to have to take another stab at
describing your problem (using concise terminology).
--
I.S.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden