Jonathan Hess wrote:
On Sep 30, 2008, at 12:01 PM, James Walker wrote:
However, I did solve my problem. I neglected to mention that I'm
working in a mostly Carbon app. When I surrounded the alloc, init,
and showWindow calls with a local autorelease pool, the problem went
away and the NSWindowController gets deallocated without funny
business. I thought I had read that it was no longer necessary to set
up my own autorelease pools.
Interesting. Was there a corresponding console message about an object
being autoreleased with no pool in place? If not, you should consider
filing a radar with a small reproducible test case.
No, there was no such console message.
I'll consider working on a radar, but I might not be able to come up
with a small test case. The app in question uses PowerPlant and
WaitNextEvent. When I tried testing with a toy Carbon app that used
RunApplicationEventLoop, the problem didn't happen.
--
James W. Walker, Innoventive Software LLC
<http://www.frameforge3d.com/>
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please 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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
