On 5/31/2016 4:53 PM, Sergey Bylokhov wrote:
On 31.05.16 0:21, Semyon Sadetsky wrote:
setDisplayMode() has been working if Xinerama is off. When Xinerama is
on it could not set some modes for the screen 0 if there were
incompatible modes from other screens in the list, and for all other
screens there were no modes.
I am talking about Xinerama mode only, since it is affected by the
fix. I am not sure I am understand what you mean above. In java we
have separate list of GraphicsDevices. Each GraphicsDevice have its
own list of modes(which returned from getDisplayModes()) all these
modes should be supported by this GraphicsDevice, so
GraphicsDevice.setDisplayMode() should not throw an exception or
should not ignore these modes.
From the bug description I see that currently in case of xinerama we
return only current mode as supported mode, so setDisplayMode() is
noop. But after the fix
This is not true. Current mode is returned for screen > 0
the list of supported modes changed and my question was: what happens
when these modes will be passed to setDisplayMode() (of course modes
and setDisplayMode should be from one GraphicsDevice object).
the same as before the fix.
---
Do you see any other concerns to the fix?
