🚀 go-pugleaf

In article <1992Aug6.000907.1895@dvorak.amd.com> rpomeroy@aunext3.cam.amd.com  
(Ron Pomeroy x(Coop)) writes:
> Hello netters,
> 
> I'm still fairly new to the appkit so bear with me.
> 
> suppose I don't check to see if infoPanel exists:
> 
> - displayInfoPanel:sender
> {
> //    if (!infoPanel) {
>       [NXApp loadNibSection:"InfoPanel.nib" owner:self];
> //    }
>     [infoPanel makeKeyAndOrderFront:NULL];
>     
>     return self;
> }
> 
> Now when I hit the Info button in the menu (in the compiled app),  
> displayInfoPanel:sender is sent and the nib is unarchived again and again.  
> 
> My question is - do all of the instances have the same id (i.e. "infoPanel) ? 

Yes, and you have a huge memory leak.  infoPanel will always point to the last  
info panel loaded, clobering your pointers to the other infoPanels.  Now, if  
you create an object with several id's, then have some code like this

- displayWindow:sender
{
	id	aNewObject;

	[myList addObject:(aNewObject = [[ANewObject alloc] init])];
       	[NXApp loadNibSection:"InfoPanel.nib" owner:aNewObject];
	return self;
}

Then each object would have their id's maintained, and by walking myList you  
can get to all the windows you have loaded/created.
	
 

--
Michael Rutman			|	moose@svcdudes.com
Cubist				|	makes me a NeXT programmer
Software Ventures		|	maker of MicroPhone II
#include <std.disclaimer>