On Jun 26, 2008, at 3:23 PM, Jelle Vandebeeck wrote:
Hi Corbin,
You should check out this link:
http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/NSSavePanel_Class/Reference/Reference.html
The word singleton is used :-)
Thank you -- I logged a bug against our
On Jun 26, 2008, at 6:23 PM, Jelle Vandebeeck wrote:
You should check out this link:
http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/NSSavePanel_Class/Reference/Reference.html
The word singleton is used :-)
As a full-text search in the Xcode doc window would ha
Hi Corbin,
You should check out this link:
http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/NSSavePanel_Class/Reference/Reference.html
The word singleton is used :-)
But I thought [NSSavePanel savePanel] returned an autoreleased object,
so I presumed no leaks c
On Jun 24, 2008, at 3:55 PM, Jelle Vandebeeck wrote:
When I try to call the NSSavePanel, I always receive some memory
leaks on it. I have no idea if they are bad or not so bad... I just
can't find a decent tutorial on the Instruments tool.
Have you tried using the "leaks" tool in instruments
On Tue, Jun 24, 2008 at 6:55 PM, Jelle Vandebeeck
<[EMAIL PROTECTED]> wrote:
> It's the [NSSavePanel savePanel that gets the leak... I know the NSSavePanel
> is a singleton, so it should always use the same instance. Is that the
> problem when I try to call it multiple times in my application?
NSS
When I try to call the NSSavePanel, I always receive some memory leaks
on it. I have no idea if they are bad or not so bad... I just can't
find a decent tutorial on the Instruments tool.
This is the code that generates the memory leak from time to time:
NSSavePanel *savePanel = [NSSavePanel