matthiasm wrote: > ... > There would be a lot of changes in the source code... .
FWIW, this is why Apple is big on getting developers to support resolution-independent user interfaces - they can then increase the display resolution (DPI) without affecting the size of the controls. IMHO, if we add support to FLTK for this (and I think we should), then we should base the scaling on the display DPI (available on all platforms) and apply it such that the app still deals with pixels at some standard resolution (96 DPI seems to be what Windows works with) and the core drawing code does the necessary scaling automatically. The only issue with this approach is that it pretty much requires that you use images for the button backgrounds, or have some way for the box functions to use the unscaled coordinates... -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike at easysw dot com Internet Printing and Document Software http://www.easysw.com _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
