On 01.06.16 9:57, Semyon Sadetsky wrote:
I don't have access to such hardware as well. I'm using linux VMs with
several virtual screens. Adding a new screen to a VM configuration can
be done in 10 seconds in most VMMs.
The result of the getDisplayModes() for 2-screen Ubuntu VM before the
fix looked like:
for device[0]: <current screen 0 mode>, <<the rest modes of
screen-0>>,<<all modes of screen-1>>
for device[1]: <current screen 1 mode>
So can you confirm that after the fix the next code will work w/o
exceptions?
http://cr.openjdk.java.net/~serb/tmp/Test.java
I am worried since we updated the enumDisplayModes(), but did not update
the getCurrentDisplayMode() which still uses the old code.
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.
Actually it seems that setDisplayMode() should not work since
JDK-8131752. probably someday we should change the code in
X11GraphicsDevice.isDisplayChangeSupported(), which skip the xinerama case.
--
Best regards, Sergey.
