[wxPython] Re: [wxPyRU] Problem with wxTreeCtrl

Things are clear now.
The difference was on the events (The win98 version has no EVT*).
I just didn't realize that events were hiding a problem with my code.

Thanks

- C r i s t i a n E c h e v e r r i a -

···

-----Original Message-----
From: Robin Dunn [SMTP:robin@alldunn.com]
Sent: Monday, August 28, 2000 3:05 PM
To: wxpython-users@wxwindows.org
Subject: Re: [wxPython] Re: [wxPyRU] Problem with wxTreeCtrl

> wxPython 2.2.1
>
> I can understand that, but this is requiered only on win98 SE,
> on win95 I don't need keep a reference inside the wxTreeCtrl, but
> only into the main frame.
>
> The next code works great on win95,
> but shows white images on win98:
>

Are you sure the code and everything else is the same on both machines?
Your sample works fine for me on win98 and win2k.

One thing to watch out for is that the thing you save the image list
reference in also has a reference. In your sample you don't explicitly
save
a reference to the frame so normally its python object would get deleted
along with the image list it has a reference to, causing the problem you
are
seeing. However in this case you are implicitly saving a reference to the
frame by attaching events to its bound methods, (the reference is in the
event table for the window.) If you comment out the EVT_*** calls below
then the image list will get deleted and the tree will not show the
images.

Robin