I have laptop with 4k display, but I have downscaled resolution to 2048x1152. The minimal size of app is then bigger than the screen and cannot be viewed.
2048x1152 on display that supports 4k

Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic
1.1.10.1
same problem here. Even worst; I can't see the "Wallet explorer" at all... I have to set my resolution to 1980x1200 at 100% to see the full window. Really annoying.
@danwalmsley anything about this in the latest Avalonia progress?
@MaxHillebrand no changes in DPI stuff (because we dont have any test vectors for it yet)
We really need to get Jumar a 4K monitor to test this.
Probably a quickfix (it do the job!) would be greatly appreciate is to allow user to set some argument to zoom out or zoom in , like on spotify (https://wiki.archlinux.org/index.php/HiDPI#Spotify) with something like "--force-device-scale-factor=1.5"
@MaxHillebrand seems like the guide @kekekeks has posted is the only solution. Linux doesnt have any standard way to get the correct DPI accurately unfortunately.
Will close issue as we now have a solution.
@MaxHillebrand @danwalmsley why are you closing this? There is no fix !
The @kekekeks solution doesnt work. Tried multiple times with different DPI values, there is absolutely no change at all.
Even if this can works for some people, It need a real solution anyway.
When I open it : wazabi UI is 300% larger than my screen. If I resize it, smallest as I can, I'm able to see ~ 80% of the UI.
@piratoskratos we are preparing a UI engine upgrade here: https://github.com/zkSNACKs/WalletWasabi/pull/3925
Can you check out that PR and build it from the source?
https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally
https://github.com/zkSNACKs/WalletWasabi#build-from-source-code
@piratoskratos we need to investigate why it didnt work. We will find a solution to this, it was closed because that should have worked..
Can you share with us an example of what you tried?
@piratoskratos iv had someone test this on linux, and the environment variable definately works... how did you set the environement variable?
remember if you set it in /etc/profile or similar you will need to restart your session before it takes effect.
@molnard potentially we could add a dialog, similar to the display settings in windows 10...

It would only need to display the monitors / resolutions, and offer user some scale factors to select.
It could be a standard dialog in Avalonia that apps like wasabi trigger, and it allows OS to be overridden in the case you get this where there is no standard way we can detect the correct DPI.
This is a rare issue and probably fixed in the future where Avalonia will be able to detect the OS settings. @danwalmsley just put it into the UiConfig.json file - do not need to create a dialog for it.
yes, I tend to agree @molnard, this is not a worth having UI clutter...
@piratoskratos iv had someone test this on linux, and the environment variable definately works... how did you set the environement variable?
remember if you set it in
/etc/profileor similar you will need to restart your session before it takes effect.
Just like it was explained. added at the bottom profile files : AVALONIA_SCREEN_SCALE_FACTORS='eDP-1=2'
tried with different values, no effect. (eDP-1 is correct as the _xrandr --listactivemonitors_ command)
Restart session or reboot, and still no effect.
Ok, I make it work by launching wasabi this way : AVALONIA_SCREEN_SCALE_FACTORS='eDP-1=2' /usr/local/bin/wasabiwallet/wassabee
Still don't know why it doesnt use my profile variables. Anyway, I'll use it this way from now.
EDIT : also export AVALONIA_SCREEN_SCALE_FACTORS='eDP-1=2' in profile file is working. the "export" keyword was required.
@piratoskratos we are currently refactoring the whole UI and the UI engine. We will focus on that as the current UI will be obsoleted. I am happy that you could make it work. thx for elaborating on it.
Most helpful comment
@piratoskratos we are currently refactoring the whole UI and the UI engine. We will focus on that as the current UI will be obsoleted. I am happy that you could make it work. thx for elaborating on it.