|
|
Many thanks. That actually worked. Tested on macOS 12.
I'm not sure what method I used, but I couldn't get it to accept any of the strings I tried to use. I also found posts (even from Apple people), stating that the system would reject even the correct string to force people to use the newer APIs that had constants for the system fonts. That evidently isn't true.
So, it seems everything can be done from the application, and FLTK doesn't need to change. :)
It might still be nice if FLTK defaults to the system UI font, though, if you feel it is worth the effort.
(minor note is that kCTFontUIFontSystem requires 10.8)
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: <fltk/fltk/issues/466/1218029956@github.com>
[ Direct Link to Message ] | |
|
| |