I finally did it :) I added third object to NIB and used it as proxy
to store data and to bind array controller. Now array controller
doesn't retain file's owner and I don't need to unbind anything, just
release file's owner when I need.
Thank you.
On Thu, Jan 15, 2009 at 7:40 PM, Keary Suska wr
I release outlets in -dealloc that gets called after I removed array
controller's binding to it.
I checked this with NSLog() calls and by breakpoint - it works. I
release my outlets there and they seems to be deallocated too (I
checked for NSView, but it seems array controller works the same way).
On Jan 15, 2009, at 10:11 AM, Vitaly Ovchinnikov wrote:
Well, I got the idea and will try this. Just one question: do I miss
something when just releasing my two outlets to two top-level objects.
Your method is more common solution, but am I wrong with mine one? I
have only two objects in my NI
Well, I got the idea and will try this. Just one question: do I miss
something when just releasing my two outlets to two top-level objects.
Your method is more common solution, but am I wrong with mine one? I
have only two objects in my NIB and release them both.
Thanks for help.
On Thu, Jan 15,
On Jan 15, 2009, at 9:04 AM, Vitaly Ovchinnikov wrote:
I'll try to describe it again. I have NIB, NSObject-based owner of
this nib and NSView + NSArrayController in that NIB.
Let's name owner of this NIB MyViewController. It has -init and -
dealloc methods
Basically, you have a classic retai
On Thu, Jan 15, 2009 at 10:04 AM, Vitaly Ovchinnikov
wrote:
> - (void) dealloc
> {
>// next two lines added after your comment
>[pView release];
>[pArrayController release];
>
>[super dealloc];
> }
This won't work as you intend, see below for explanation.
>
> In the main window c
I'll try to describe it again. I have NIB, NSObject-based owner of
this nib and NSView + NSArrayController in that NIB.
Let's name owner of this NIB MyViewController. It has -init and -dealloc methods
-(id) init
{
self = [super init];
[NSBundle loadNibNamed:@"MyView1" owner:self];
retu
On Wed, Jan 14, 2009 at 11:58 PM, Vitaly Ovchinnikov
wrote:
> Well, OK. I am ready to release all root objects myself. Just tested
> with subclassed NSView from that NIB - it didn't get released
> automatically.
> So I added several -release calls to -dealloc method of my NIB's owner
> and now it
Well, OK. I am ready to release all root objects myself. Just tested
with subclassed NSView from that NIB - it didn't get released
automatically.
So I added several -release calls to -dealloc method of my NIB's owner
and now it will release everything.
But the problem is still there: -dealloc of my
On Wed, Jan 14, 2009 at 3:51 PM, Vitaly Ovchinnikov
wrote:
> Hello all,
>
> I have a custom-loaded NIB file with NSView and NSArrayController.
> Array controller is bound to file's owner (NSObject's derived class)
> and use some keypath for contentArray. The problem is when I close a
> window and
I just found a solution, but I don't like it. I added method
-beforeRelease to my view controller where I send -unbind: to my array
controller. I call this method from my window controller just before
-release call. This helps. But looks ugly... Does somebody know better
way?
On Thu, Jan 15, 2009
Hello all,
I have a custom-loaded NIB file with NSView and NSArrayController.
Array controller is bound to file's owner (NSObject's derived class)
and use some keypath for contentArray. The problem is when I close a
window and main window controller tries to release this file's owner -
array contr
12 matches
Mail list logo