On 5/31/2016 6:22 PM, Sergey Bylokhov wrote:
On 31.05.16 18:05, Semyon Sadetsky wrote:
On 5/31/2016 5:18 PM, Sergey Bylokhov wrote:
On 31.05.16 17:09, Semyon Sadetsky wrote:
This is not true. Current mode is returned for screen > 0
Does it mean that this part in the description is incorrect?
it depends on the OS and its configuration I guess. For Ubuntu 14/15 and
OEL 6/7 it is not correct.
Then I suggest to check the system where the bug was reproduced for
the first time.(bug was filed by SQE team).
Can you please provide the output of the test from the CR before/after
the fix on your system?
it is not necessary. You can run the provided test before and the fix
and see that the list returned by getDisplayModes() is identical to
xrandr output for any screen number on linux. There is nothing else to
prove for this bug fix.
============================
Compile and run it on a system with two displays. Here is output when
both display are switched on (note: only current resolutions are
listed):
Device: X11GraphicsDevice[screen=0]
Resolutions:
966x1280
Device: X11GraphicsDevice[screen=1]
Resolutions:
920x1280
============================
Then try to switch one of the displays (e.g., System
Settings->Displays etc.) off and run the test again. The test output
looks like:
Device: X11GraphicsDevice[screen=0]
Resolutions:
966x1280
960x1280
768x1024
600x800
480x640
============================
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?
