|
|
On 1/21/23 10:01, Greg Ercolano wrote:
On 1/21/23 08:37, 'Matthias Melcher' via fltk.general wrote:
The current solution is not the best solution, and it should not
break existing code. The background is the use of FLUID and
other tools in the command line. Depending on the OS, opening a
connection to the display may throw an error if the tool is
intended for the command line. So we try to leave all measuring
of fonts and other machine relevant data until the app calls
`show()`. This works generally very well, because font size
commonly don't need to be known until a widget is shown or
drawn. But as we see here, this is not always the case and can
not always be expected from the user.
I think too, IIRC, the font system initialization overhead is
significant enough on some
platforms that it should be delayed until absolutely
necessary. Esp. so that in FLTK applications
that don't even draw any text (pure graphics, like a
speedometer on embedded hardware)
the overhead can be avoided.
Ugh, fixing omissions in bold to my above paragraph that
I musta written while still waking up..
--
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/1765872c-daf8-5a0e-bd40-33b43be4ba25%40seriss.com.
[ Direct Link to Message ] | |
|
| |