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
Seems like it is possible now:
We have in the fltk html doc an Chapter H for migrating from 1.1 to 1.3
Maybe it should be updated/completed ?
L
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
Yes, this should be part of the Doxygen documentation. Silly, but Doxygen
does provide a \todo and \deprecated tag which generates a list of thos
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
Adding a CHANGES.API file or whatever to maintain the API changes would be
also error prone because we could easily forget to update it, while
up
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 documentat
