I tried switching over to the SuperImage class. It works wonderfully...except when it doesn't.
Now, my BitmapData is no longer getting set to null (a step in the right direction). However, only one SuperImage can reference the BitmapData at a time. I have a SuperImage visible in a scrollable Tree container. When I double-click the SuperImage, a Window opens and binds to the same BitmapData. When this Window opens, the SuperImage in the Tree container turns to black (but not null), and the SuperImage in the Window shows up properly. If I then scroll the Tree container so that the SuperImage in the Tree gets re-rendered, the Tree's SuperImage displays properly and the one in the Windows turns black (but not null). It seems like whichever object references the Bitmap most recently gets a lock on it or something. I think the problem is with the Bitmap class (although clearly something is wrong with the Image class as well, since SuperImage corrects some of the issues). Any other suggestions? --- In [email protected], leds usop <[EMAIL PROTECTED]> wrote: > > i'd rather use ely's superimage ^^ or a subclass at that - but that's just me. >
