NoiseTorch icon indicating copy to clipboard operation
NoiseTorch copied to clipboard

Scaling

Open denzanine opened this issue 3 years ago • 5 comments

NoiseTorch doesn't seem to automatically detect my system's scaling factor. I'm running Ubuntu 20.04 with fractional scaling on (%150) on a 4K monitor. The UI is very small. Is there a way to update it manually? Thank you!

Screenshot from 2021-05-03 17-30-39

denzanine avatar May 04 '21 00:05 denzanine

How does this work for other apps? It seems relatively simple for us to just add a config value and blow up the UI by it, but i feel like this is something that really should just work. Though from a quick google I only find GTK/Qt specific environment variables.

I don't have anything that would require scaling, so I have no experience with it. Is this really how it generally works on linux, that you need to update the scaling factor per app?

lawl avatar May 04 '21 14:05 lawl

I imagine this would be something to be handled by nucular.

Because nucular is based on Nuklear, I did find these issues: Immediate-Mode-UI/Nuklear#220 Which links: vurtun/nuklear#123 and vurtun/nuklear#74

There are a lot of complex issues involving scaling, see Qt - High DPI Displays

Lot of info here. https://wiki.archlinux.org/title/HiDPI

Different display servers, and multiple monitors at different dpi settings, I don't think a one time scale check would be sufficient. Looks like a mess honestly.

bluthen avatar Jun 02 '21 03:06 bluthen

Nucular does have a scaling factor i can set. But indeed the reason i'm asking is because it doesn't seem as trivial as that to me. E.g. what if you have a multihead setup where one display is hidpi and one isn't and you have your window placed across both?

Maybe that's too much of an edge case, but as i don't have a hidpi setup i really have no clue or intuition how it generally behaves.

lawl avatar Jun 02 '21 03:06 lawl

I agree with you that it is not trivial.

I think I've been spoiled by Qt that tries to handle this automatically for me, I guess that is why I mentioned it could be handled on the nucular side, much like it is handle on the Qt side where the application that uses Qt doesn't need to do anything to support scaling.

You can still scale a lower dpi monitor for testing. Can also use a VM with a virtually scaled display that then you scale (even multiple monitors). I don't mean you as in you specifically just the general you.

I do not think think it is too much of a edge case of multiple monitors with different dpi settings.

bluthen avatar Jun 02 '21 03:06 bluthen

I have this issue too.

redthing1 avatar Nov 12 '22 23:11 redthing1