Re: Plugin not receiving -dealloc call at the expected time
Re: Plugin not receiving -dealloc call at the expected time
- Subject: Re: Plugin not receiving -dealloc call at the expected time
- From: Darrin Cardani <email@hidden>
- Date: Mon, 17 Nov 2008 09:48:45 -0800
On Nov 16, 2008, at 8:50 AM, David Yamnitsky wrote:
Hi everyone, I'm building a plugin which opens a separate window.
It all works fine, except I'm having the problem that when the
effect is deleted, the window remains open. Any attempt to
manipulate something in the window which makes an FxPlug API call
crashes the app. I consulted the FloatingWindow example code, which
just releases the window when -dealloc is sent to the plugin object,
which is the same thing I'm doing. I did some digging, and found
that the FloatingWindow example receives the -dealloc call right
when the effect is deleted, but my plugin receives that call rather
spontaneously, either when the app is quit or when another effect is
applied. Why is this? Could it be because my plugin is dynamically
registered? (that seems to be the only obvious difference between
the FloatingWindow example and my code).
David,
One thing to look out for is make sure none of your objects are
retaining your plugin instance. If you've retained it, then when the
host app releases it, it will still have at least 1 reference and
won't be deallocated.
Darrin
--
Darrin Cardani
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden