search

airsdk / Adobe-Runtime-Support

Report, track and discuss issues in Adobe AIR. Monitored by Adobe - and HARMAN - and maintained by the AIR community.
201 stars 11 forks source link

Stage.contentsScaleFactor always 1 on Linux (HiDPI support) #1123

Open pol2095 opened 3 years ago

pol2095 commented 3 years ago

Description

Stage.contentsScaleFactor always 1 on Linux (Ubuntu 20 and Fedora 34 : display scaling is 200%) HiDPI support for 4K screen

I added in the app descriptor : <requestedDisplayResolution>high</requestedDisplayResolution>

my app is very small vs the same app on Windows or Mac.

I found a workaround here, but it's not perfect.

xrandr -s 1920x1080
/path/to/executable
xrandr -s 3840x2160

Thanks.

pol2095 commented 3 years ago

Any news about this problem ?

ajwfrost commented 3 years ago

Hi @pol2095 - we had been looking into this and were trying to get the application scaling to work but ran into some issues.. I'll see whether the developer looking at this has had any further luck..

pol2095 commented 3 years ago

Air app use gtk2, Ubuntu app using scaleFactor seems use gtk3.

ajwfrost commented 3 years ago

Yes that's what the developer has told me, he was looking at whether there are any cunning workarounds we can try to apply to get it to manually scale. But we can also look at whether it's feasible to update to gtk3 I guess..

pol2095 commented 2 months ago

Any news about this Feature ?

Using Fractional Scaling it's possible to solve the problem (tried on Ubuntu).

ajwfrost commented 2 months ago

We are progressing on the GTK3 work, so once that's done we can set this up properly..

pol2095 commented 2 days ago

Any news of GTK3 on AIR SDK for Linux ? Why did you choose GTK3 and not GTK4 ?

ajwfrost commented 2 days ago

Hi

Sorry for the delay - just spoke with the guy who had done this, it's pretty much there but needs to be integrated into our latest codebase and then a lot of testing...

The switch from GTK2 to GTK3 looked a lot easier than the switch from GTK3 to GTK4! So mostly it was to make it easier to implement the changes; we didn't actually need any of the functionality from GTK4.

Our plan at the moment is to put this change in to our 51.2 branch and then probably push out a beta of it, as there are quite a few changes going in there. So we'll also push out another (lower-risk) update on 51.1 in the meantime..

thanks