Greg Ercolano wrote: > Albrecht Schlosser wrote: >> because now the children() widget count would _not_ >> anymore count the 2 scrollbars if I understood his >> CHANGES.composite and related topics where he talks >> about now having to adapt existing code with children-2() offset change. > > Is 1.3.x supposed to break existing apps? > > A while ago it sounded like 1.3.0 was going to be the > time to implement long pending ABI-breaking fixes, > large scale mods like utf8. > > I wasn't aware we were also going for code breaking mods > in this release. > > What's the "general" definition of what 1.3 will be bringing?
I'd say the goal is to avoid breaking things unnecessarily, but there might be some side-effects of design changes (UTF-8, this Fl_Scroll stuff) which may require small code changes. That said, I don't know how much existing code exists that tries to directly manipulate the child() array of a Fl_Scroll widget. -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike at easysw dot com _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
