Re: One Shot Windows: WARNING

2009-02-11 Thread Michael Ash
On Wed, Feb 11, 2009 at 4:06 PM, Seth Willits wrote: > On Feb 10, 2009, at 9:12 PM, Michael Ash wrote: > >>> The behavior of non-one shot windows is obviously not clear. >> >> Forgive me for saying this, but this sounds a lot like the common >> newbie complaints about Cocoa memory management. > >

Re: One Shot Windows: WARNING

2009-02-11 Thread Seth Willits
On Feb 10, 2009, at 9:12 PM, Michael Ash wrote: The behavior of non-one shot windows is obviously not clear. Forgive me for saying this, but this sounds a lot like the common newbie complaints about Cocoa memory management. It's more than memory management. For example, why does a non-one-s

Re: One Shot Windows: WARNING

2009-02-10 Thread Michael Ash
On Tue, Feb 10, 2009 at 3:38 PM, Seth Willits wrote: > On Feb 10, 2009, at 10:30 AM, Michael Ash wrote: > >> I downloaded the example, ran it, and reproduced the crash. >> >> I then enabled zombies and ran it again. The crash message said: >> >> 2009-02-10 13:27:16.566 DocumentTest[97982:813] ***

Re: One Shot Windows: WARNING

2009-02-10 Thread Matt Neuburg
On Tue, 10 Feb 2009 13:30:52 -0500, Michael Ash said: >Connected it in the nib, then implemented -dealloc: > >- (void)dealloc >{ > [tv setDataSource: nil]; > [super dealloc]; >} > >Crash went away, again exactly as predicted. > >The problem is simply that the one shot setting ends up making the >t

Re: One Shot Windows: WARNING

2009-02-10 Thread Seth Willits
On Feb 10, 2009, at 10:30 AM, Michael Ash wrote: I downloaded the example, ran it, and reproduced the crash. I then enabled zombies and ran it again. The crash message said: 2009-02-10 13:27:16.566 DocumentTest[97982:813] *** -[MyWindowController tableView:objectValueForTableColumn:row:]: mess

Re: One Shot Windows: WARNING

2009-02-10 Thread Michael Ash
On Tue, Feb 10, 2009 at 1:18 PM, Matt Neuburg wrote: > On Tue, 10 Feb 2009 11:12:17 -0500, Michael Ash > said: >>On Tue, Feb 10, 2009 at 1:02 AM, Matt Neuburg wrote: >>> Actually, having looked at your example, I reproduced the crash from the >>> bottom up by starting with the Document Architect

Re: One Shot Windows: WARNING

2009-02-10 Thread Matt Neuburg
On Tue, 10 Feb 2009 11:12:17 -0500, Michael Ash said: >On Tue, Feb 10, 2009 at 1:02 AM, Matt Neuburg wrote: >> Actually, having looked at your example, I reproduced the crash from the >> bottom up by starting with the Document Architecture template. >> >> I created a window controller class, made

Re: One Shot Windows: WARNING

2009-02-10 Thread Michael Ash
On Tue, Feb 10, 2009 at 1:02 AM, Matt Neuburg wrote: > Actually, having looked at your example, I reproduced the crash from the > bottom up by starting with the Document Architecture template. > > I created a window controller class, made it the Document nib's owner, > overrode makeWindowControlle

Re: One Shot Windows: WARNING

2009-02-09 Thread Matt Neuburg
On Sat, 7 Feb 2009 21:06:20 -0800, Seth Willits said: >On Feb 7, 2009, at 8:45 PM, Matt Neuburg wrote: > >>> In my case, I have a document window with a table view in it, where >>> data source and delegate are the window controller. If the window is >>> oneShot NO, then the window controller is de

Re: One Shot Windows: WARNING

2009-02-07 Thread Seth Willits
On Feb 7, 2009, at 8:45 PM, Matt Neuburg wrote: BAD! BAD! BAD! BAD! In my case, I have a document window with a table view in it, where data source and delegate are the window controller. If the window is oneShot NO, then the window controller is deallocated, but the views in the window are stil

Re: One Shot Windows: WARNING

2009-02-07 Thread Matt Neuburg
On Sat, 7 Feb 2009 17:32:58 -0800, Seth Willits said: >BAD! BAD! BAD! BAD! >In my case, I have a document window with a table view in it, where >data source and delegate are the window controller. If the window is >oneShot NO, then the window controller is deallocated, but the views >in the window