RE: [flexcoders] PopUpButton issue

2008-01-16 Thread Deepa Subramaniam
This chunk of code was added on purpose, to avoid problematic memory leaks with popup components. In Jira you can see it was fixed to address SDK bug 13104. We were not correctly unregistering popup children when necessary. Your workaround is correct, so feel safe using it :)

Re: [flexcoders] PopUpButton issue

2008-01-16 Thread Scott Melby
Deepa - Thanks! It seems you could avoid the memory leak without nulling _popUp couldn't you? i.e. just call PopUpManager.removePopUp(_popUp) without the following line that nulls the reference. Is that not right? Scott Scott Melby Founder, Fast Lane Software LLC

RE: [flexcoders] PopUpButton issue

2008-01-16 Thread Deepa Subramaniam
, January 16, 2008 12:47 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] PopUpButton issue Deepa - Thanks! It seems you could avoid the memory leak without nulling _popUp couldn't you? i.e. just call PopUpManager.removePopUp(_popUp) without the following line that nulls