DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2411 Version: 1.3-feature > Better to focus on getting a single, standard colorspace working right > for all applications (sRGB) and *maybe* look at alternate colorspace > support in the future. Thats a good step toward a CM policy. Great. Some remaining questions: How can a user programmatically see that wide gamut support is there or not? Which widgets are going to be affected? A function like the following could answer those questions in a upward compatible way: int fl_color_space ( Fl_Widget * my_widget, void ** returned_profile_block, size_t * returned_size ); useful results: * device RGB - return no profile (Win32, X11) * sRGB - return a ICC profile blob (osX SL), that can be static * wide gamut - return in the future the actual set profile Maybe its more beautiful to have a Fl_Widget::color_space( .. ) . Link: http://www.fltk.org/str.php?L2411 Version: 1.3-feature _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
