DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR New]

Link: http://www.fltk.org/str.php?L2563
Version: 1.3-feature


Well, I may be missing a point, but I don't see any benefit in un-inlining
these methods. I presume that we will need new (i.e. additional) methods
anyway if we extend the functionality to use Fl_Image or others for the
icons. So, what would we gain if we change the existing methods now?

That said, we can always add new methods w/o breaking the ABI, as long as
they are not virtual and/or need additional member variables. I supect
that we might need other member variables if we add alpha masks (as
distinct objects), or at least some more bit flags to know what kind of
image/icon object we have. Thus, I believe that the existing methods that
deal only with void* pointers won't change if we add other icon formats
and methods.

I suggest to move this STR to 1.4 (or to close it), because we can't know
in advance which new functionality we will need, before we have proposals
(and maybe patches) for a concrete API extension.

Please explain why you think that your patch should be applied now, and
what I may have overlooked.


Link: http://www.fltk.org/str.php?L2563
Version: 1.3-feature

_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to