> BTW, is there any sense of when FLTK > 1.3.0 will be released? Not so far - just "when it's done"... Help always welcome, of course.
> I'm trying to gauge whether or not > we should adopt it yet. It works OK for me. The API seems to be largely stable, and pretty well back-compatible with fltk-1.1. There is change ongoing, but so far even the new cocoa OSX stuff, which was a big change, has not caused my code to fail. What would prevent you adopting it, though? In the mean-term, you can probably archive one of the weekly snapshots, if you want to be sure of having a solid baseline... SELEX Galileo Ltd 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 fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
