RFR: 8280991: [XWayland] No displayChanged event after setDisplayMode call [v2]

Alexander Zvegintsev azvegint at openjdk.org
Tue Mar 4 15:59:54 UTC 2025


On Mon, 3 Mar 2025 21:19:26 GMT, Phil Race <prr at openjdk.org> wrote:

> What about, if we are on Wayland, behave the same in single-screen as you say happens any way with multi-screen - report only one resolution - the current / default one ?


This effectively sounds like `GraphicsDevice#isDisplayChangeSupported() == false`.

> I suggest this in part because I am not sure what the impact is of having the resolution be "emulated". If the app, and AWT think there's a different resolution than there really is, rendering quality could be affected.

I've so far only been able to think of one case where such a screen resolution change might be needed at all:
Some game that can't have decent performance at the native screen resolution.

So I left this option with the ability to change the resolution. Yes, rendering quality may drop, but we can always go back later to the option where the only available resolution is the native one.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/23774#issuecomment-2698135159


More information about the client-libs-dev mailing list