<AWT Dev>  Review request for 8169133: This time, on Windows: java/awt/Robot/SpuriousMouseEvents/SpuriousMouseEvents.java
Sergey.Bylokhov at oracle.com
Fri Nov 25 13:13:58 UTC 2016
On 24.11.16 22:21, Semyon Sadetsky wrote:
>>>> All robots may be used to address any area of the desktop regardless of
>>>> the screen constructor argument.
>>>> The coordinate system is the only aspect the screen argument affects.
>>> This statement means that this constructor will have any effects when
>>> used for the system where each screen "use different coordinate systems
>>> to act as independent screens" this is not true for windows. It is true
>>> only for the screens on unix when each screen will have its own
>>> coordinate space, and which space will be used depends from on what
>>> screen the robot was created.
>> Then JDK-8013116 was fixed the request for specification update was
>> created: https://bugs.openjdk.java.net/browse/JDK-8033128
> Different coordinate system simply means different coordinate origins.
> This is the most natural behavior for the robot created for certain screen.
And if both screens have the same coordinate system simply means that
they have same coordinate origins.
> I didn't see a desktop within the OSes supported by JDK9 where multiple
> screens are treated as a separate displays rather then one extended
Such configurations exists, even if default configs supported by Oracle
have Xinerama does not mean that it was not supported in past, and is
not supported by OpenJDK in general.
> It seems JDK-8013116 should be reworked to correspond to the current
> state of multiscreen concept on the supported platforms.
Best regards, Sergey.
More information about the awt-dev