Re: [Foxgui-users] High DPI support / Wayland support

[<je...@fo...>]

On 2025-12-03 10:56, Roland Plüss via Foxgui-users wrote:
> What are the plans for supporting high DPI displays (4k) displays and 
> wayland?
> 
> I've used FOX right now on X11 with a regular 1980 monitor but now I
> want to also support it on a newer 4k monitor with HDR support. 4k
> requires global scaling to be respected (typically 150-200% for 4k).
> HDR requires wayland to be used. It would be nice to know if these
> features are planed for the future or not.

Really, the only problem is, technically, the icons.  We can set DPI via
FOX ControlPanel application; you can also pick larger fonts, and 
widgets
should automatically resize based on the fonts and contents.

Your own application can of course simply use bigger artwork, perhaps 
via
using FXFileAssociations, FXIconSource and FXIconCache.

FXIconSource::loadScaledIconFile() can load and then scale down an icon, 
so
making in smaller for lower DPI screens.  You could also set icon search 
path
to locate different size icons for different screen resolutions.

As to the built-in icons, these are currently hardwired via reswrap.  
Perhaps
in future we might have alternate artwork for high-DPI screens, but 
drawing
those is a LOT of handi-work and currently I don't have the time.

If anyone knows of good [free/libre] collections then pls point me to 
that.

I still like the idea of built-in icons, and we favor icons that don't 
need
external libraries for support, so people that want minimal overhead can
have lean-and-mean versions.

To that end, we recently implemented PNG support directly into FOX, but 
right
now it still requires an external library for compression.  Maybe next 
step
is to get rid of this as well and use a built-in LZW compressor.

The embedded PNG implementation is actually a bit faster than libPNG, 
and
with embedded LZW compression and updated CRC32 support [via 
"carry-less"
GF multiply] we can increase speed even more.  libz is not fastest, 
because
its a bit old and not fully taking advantage of modern vector-support.

[BTW, does anyone know if zstd compression produces a bitstream
compatible with libz?? Never found anything about this.  I suspect the
answer is no, which means we would have find something else].

Recently implemented QOIF is also a good candidate for icons, its not as
good as PNG but for many images it does a very decent job, its typically
just a big bigger than PNG.

         -- JVZ