wxperl-users

[wxperl-users] How to destroy instances of Wx::PlEvent / Wx::PlCommandEvent ?

[Lucian D. <lu...@eu...>]

Seems that the custom events derived from Wx::PlEvent / Wx::PlCommandEvent are  
not destroyed until the global destruction phase, when interpreter exit. How 
can be freed the memory they occupy before that END phase ?

Best regards,
  Lucian Dragus

Re: [wxperl-users] How to destroy instances of Wx::PlEvent / Wx::PlCommandEvent ?

[Lucian D. <lu...@lu...>]

>> Seems that the custom events derived from Wx::PlEvent / Wx::PlCommandEvent are
>> not destroyed until the global destruction phase, when interpreter exit. How
>> can be freed the memory they occupy before that END phase ?

>   They are supposed to be destroyed when the last reference goes away.
> I will investigate. Do you have some (simple) example code?

Yes, I extracted something from my app.
I finded that custom events are not destroyed automatically when I
attached some object to events ($evt->{prop} = $obj), but they was not
released until exit.

Thank you,
  Lucian Dragus

Re: [wxperl-users] How to destroy instances of Wx::PlEvent / Wx::PlCommandEvent ?

[Mattia B. <mat...@li...>]

On Sat, 4 Nov 2006 18:42:05 +0200
Lucian Dragus <lu...@lu...> wrote:

  Hi,

> >> Seems that the custom events derived from Wx::PlEvent / Wx::PlCommandEvent are
> >> not destroyed until the global destruction phase, when interpreter exit. How
> >> can be freed the memory they occupy before that END phase ?
> 
> >   They are supposed to be destroyed when the last reference goes away.
> > I will investigate. Do you have some (simple) example code?
> 
> Yes, I extracted something from my app.
> I finded that custom events are not destroyed automatically when I
> attached some object to events ($evt->{prop} = $obj), but they was not
> released until exit.

  This should be now fixed in CVS (I also added a test case).
Could you please test with current CVS and report if it works
for you too?

Thanks!
Mattia