Recently, when chasing the font size differences between the wayland and xcb Qt backends, I ended up normalizing on the wayland sizing when bypassing the backend's font metrics calculation (#272). Unfortunately, the wayland backend was not rendering the font sizes correctly, and it was a mistake to duplicate its behavior.
* Assume a virtual DPI of 72 pixels/in instead of 96 when compulting font size
- Based on testing, this produces the correct font size
- Updated reference labels.
* No longer need to scale fonts when importing glabels-3 files.
- The glabels-3 font sizes were correct afterall! (#306)
- No longer need to compensate for scale factor in unit tests when importing glabels-3 files.
- This originally showed up as fonts rendering differently on X11 than Wayland. (#230)
- Setting font size in points should be device and back end independent, however the same exact font face and size, on
the same machine, sometimes results in different font metrics between the xcb and wayland Qt back ends.
- Setting font size in pixels, assuming a virtual DPI of 96 pixels/inch, results in consistent font metrics and rendering
between these back ends. Furthermore, this virtual DPI works for either on-screen or hi-res printer QPainter contexts.
- This virtual DPI seems to work correctly with some limited testing with Windows and MacOS.
- Add rendering tests to build-tests CI script.
Jaye Evins