MacArthur, Ian (SELEX GALILEO, UK) wrote: >> This is a common need and trivial to code. > > Hmm, is it though? I'm not sure... In practice, I've seldom found it > necessary to detect most (any?) of these things at runtime.
Yes, I think so as well. >> Why not make it an FLTK class? Something like this... > > I guess we'd accept contributions in this area. I guess we shouldn't. This would open a can of worms, add platform-specific coding, and would be of no use for FLTK internally. Thus, this should IMHO be handled in user code and not be part of the FLTK lib. Albrecht _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
