Fabien Costantini wrote:
>> Albrecht Schlosser wrote:
> ./..
>>> Currently the Fl_Shared_Image would be removed from the image
>>> list only if release() would be called, but we'd have a problem
>>> anyway, since there might be other pointers to the shared image.
>> Yup, and we'll just have to educate users about this - don't use
>> delete on shared images, don't mix delete with retain/release, etc.
>>
>> --
>> ______________________________________________________________________
>> Michael Sweet, Easy Software Products mike at easysw dot com
> Wouldn't it be a nice thing to make the Shared image destructor protected ?
That's how it is implemented now. We just can't do this for the base
class (Fl_Image) since it and the other non-shared images can be used
as global or stack-based variables, e.g.:
Fl_Pixmap foo_xpm(foo_data);
--
______________________________________________________________________
Michael Sweet, Easy Software Products mike at easysw dot com
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
