Albrecht Schlosser schrieb:
> On 15.04.2012 12:26, Edzard Egberts wrote:
>>> (1) Adding data to Fl_Widget would change the ABI, and we probably
>>> wouldn't do this, because this would only become generally usable in
>>> a new FLTK version (1.4 or 3.0), but ... see (2).
>>
> The label (struct Fl_Label) is part of Fl_Widget, hence the ABI would
> change anyway.
>> Fl_Fontsize labelsize() const { return label_.size(); }
>
> I don't think that this would break code (i.e. change any API or
> semantics), since the Fl_Label struct is private in Fl_Widget
>> Fl_Fontsize textsize() const { return label_.textsize(); }
>
> The former. The latter would mean that you can't have different text
> and label sizes, which would definitely be wrong.
No, the latter means, that there are is additional "Fl_Fontsize
textsize_;" inside of Fl_Label. The new data were not added to
Fl_Widget, but to Fl_Label.
> Probably okay for the API, but not for the ABI. We'd need to add new
> members (at least one) to Fl_Widget. Adding the textsize() method to
> Fl_Widget wouldn't harm, though.
I think it's possible to push all changes into Fl_Label, so there are no
changes of API. But would this break ABI? That would mean, there is no
possibility remaining to realise it without breaking ABI.
This is first answer, but comments to the rest of your posting would
depend on this ABI question.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
