> > 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.
For what it's worth, so far all of my 1.1.x code builds and runs OK with 1.3 with no changes. But I don't use Fl_Scroll at all, and I think that is one area where we have deliberately changed the API in an attempt to make it more consistent, and Albrecht/Fabien are engaged in moves to rationalise that further... -- Ian SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
