Display problems Windows

[d.healey]

@Oli-Ullmann Are you using a panel to create the grid or are those individual buttons?

[Oli Ullmann]

@d-healey
These are individual buttons. I know, a panel would probably have been better, but at the moment I have solved it with buttons...

[d.healey]

Yeah a panel is definitely a better option... it's not too late to change your ways :D

You can try Content.setUseHighResolutionForPanels(true); although as the name implies I think it only affects panels but maybe it also applies to laf for buttons - I assume those buttons are using laf?

[Oli Ullmann]

@d-healey
Maybe the variant with panel will come in an update...

Yes exactly, the buttons use laf and are drawn according to their status (0/1).

Many thanks for your idea! I'll try it out right away.

[aaronventure]

@Oli-Ullmann could just be the way scaling works differently on different systems.

There are for sure some visual differences between macOS and Win. You'll also find that some font sizes are not exactly the same, kerning pairs not working on Win, gradients being worse on Windows etc.

[Oli Ullmann]

@aaronventure
Yes, I have included the font so that it is displayed in the same way on both systems. (Hopefully)

Also, the download behavior on the Mac seems to be different than on Windows... There seem to be some differences.

[d.healey]

@Oli-Ullmann said in Display problems Windows:

Yes, I have included the font so that it is displayed in the same way on both systems.

Test it, I find I often have to adjust the size of fonts on Windows to match the appearance on Mac and Linux.

[Oli Ullmann]

@d-healey
Thanks for the tip! I will definitely do it.

[aaronventure]

@Oli-Ullmann said in Display problems Windows:

Yes, I have included the font so that it is displayed in the same way on both systems. (Hopefully)

When it does happen, including it won't make a difference; it comes down to how the OS renders the typeface. I don't know whether it's a format issue, or some internal settings or metadata of the file.

[Oli Ullmann]

@aaronventure
Ah, good to know! :-)

[Oli Ullmann]

@d-healey @aaronventure
Just for your information: The solution was to use g.fillRect instead of g.fillAll.

[d.healey]

@Oli-Ullmann Oh that's interesting!

[Oli Ullmann]

@d-healey
It's actually not the first time that “fillRect” works better than “fillAll” for me. I can't remember why I changed my mind before, but as I said, it has happened before. Also on the Mac.