Radio App - Overlapping text

Radio app UI has overlapping text fields. Specifically, the "87.5" and "MHz" strings overlap, same for the other frequency labels.

Analysis so far:

Volker: At least I found the difference that causes the messed up layouts, the Style
on the emulator image (and presumably the target too) loads "AutoConfig.qml", rather than "Config1920x1080.qml" (which is the one that works fine on desktop). The attached screenshot shows the values loaded in the broken case, maybe that helps somebody who knows the Neptune code better than me already. I'll keep digging too though.

Nedim: In the am-config.yaml file you have the property ‘styleConfig’ and if you want that target reads the Config1920x1080 explicitly, simply assign:

styleConfig: "Config1920x1080.qml”

Volker: It helps in the sense that I now can reproduce Alistair's screenshot exactly, in the emulator (but not on the desktop).

Looking at the tuner slider frequency labels (see attached screenshot), the font for the "MHz" label is calculated to 14px in the style (which seems
reasonable), but the size that is actually used ends up being much larger,
drawing outside of its actual item geometry (the area in the center with the diagonal lines).

Vladimir: Which resolution is set on the emulator? Which DPI is it? What does Alistair have? Neptune cannot scale in the current version, IIRC, you always have to explicitly define what is connected.

Volker: The emulator seems to provide 1280x800 here, for DPI however I get conflicting data, eglfs debug output says 100dpi, the [Q]Screen objects report 146dpi.

Is anyone able to reproduce this on your side?

Volker: Here's another finding that might help: The larger font size is actually not the one we set in TunerSlider, that one is correct and apparently also not wrongly DPI-converted. What we see is the default font size of the Label. That is counter-intuitive since one would assume the outer binding in TunerSlider to prevent that from being used. But since we have a property alias on font, not font.pixelSize this doesn't seem to be the case. Removing the default for font.pixelSize in Label solves this, but of course has other side-effects.

I suspect the different behavior between host and target comes from
AutoConfig.qml being used on the target, which recomputes the default font sizes later, while Config1920x1080.qml has those constant. But I haven't verified that yet.