| |
| |
On 5/17/21 12:54 AM, Manolo wrote:
That code uses GDI+ only when it improves the quality of
current drawings,
that is, when drawing non horizontal nor vertical lines or
when drawing curves.
All the rest (e.g., text, images, horizontal and vertical lines,
rectangles) are
processed unchanged by GDI.
[..]
GDI+ is supported from Windows XP and up. When GDI+ isn't
available, the modified
code falls back to GDI. Thus FLTK remains compatible with
Windows 95.
Both configure-based and CMake-based builds are taken care
of.
My vote is +1
Regarding GDI, I'm undecided (+0/-0) as I've not tested for
slowness
with the latest incarnation, but perhaps that'd be a good
default since
GDI is part of the OS (assuming it's not slow). Just be sure
there's a flag
to disable it, as some might run into trouble with GDI and want
to turn it off.
I think Bill brought up cairo on X11, which may have tainted
some other folk's
votes after that; everyone who voted with cairo in mind should
be aware Manolo's
OP never mentioned cairo.
Regarding cairo, I'd be a big -1 for cairo being on by default
(if cairo is present),
as I have cairo installed just for testing, but I definitely
don't ever want it to be on
"by default", as it's definitely slow and heavy. Some systems
may come with cairo
pre-installed, so a default cairo on would automatically
involve cairo if it were default.
IMHO cairo should never be the default. But if you want, cmake
could print a note
in a highlight color indicating "Cairo found but not enabled.
(If you want antialiasing
in FLTK, you can enable cairo with -xxx)"
--
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/d9ce8e9c-9c29-c4b2-d495-a6f8bdaa05f6%40seriss.com.
[ Direct Link to Message ] | |
|
| |
