DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L1942 Version: 1.3-current All API changes in FLTK 1.3 and higher should be documented thoroughly, when/while they are done, for at least two reasons: (1) later documentation is error prone, changes could be forgotten. (2) svn users and beta testers should have a documentation at hand, when they want to try and test current svn versions with real applications. I propose a (maybe) preliminary file like CHANGES.API or something else, but in the final release there should be a chapter in the docs, that reflects the code changes and caveats that need to be checked when switching from 1.1 to 1.3, as there was one for the 1.0 to 1.1 transition, IIRC. For the preliminary CHANGES.API file, it would be sufficient to add all changes as in the CHANGES file, but with some explanation, e.g.: Fl_Scroll::scroll_to(int x, int y) replaces Fl_Scroll::position(int x, int y) [link to docs]. Please be aware that you need to change your application's code for all Fl_Scroll-derived widgets. The compiler may not detect any errors, because your calls to position(int x, int y) might end up calling Fl_Widget::(int x, int y) [link to docs], which is why this change was needed, because Fl_Scroll::position(x,y) overloaded Fl_Widget::position(x,y), but with a completely different function. -- This CHANGES.API file should be announced in fltk.development, and also in fltk.general. Note: I used priority 5 (critical), because this should be done ASAP. Feel free to lower the priority, once there is an established standard. Link: http://www.fltk.org/str.php?L1942 Version: 1.3-current _______________________________________________ fltk-bugs mailing list fltk-bugs@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-bugs
