Looks fine.
On 28/12/15 17:47, Alexander Scherbatiy wrote:
Could you review the updated fix:
http://cr.openjdk.java.net/~alexsch/8143316/webrev.01
- DefaultMouseInfoPeer is removed from the SunToolkit and
WMouseInfoPeer is added to the WToolkit
- Screen devices initialization is added
Could you review the updated fix:
http://cr.openjdk.java.net/~alexsch/8143316/webrev.01
- DefaultMouseInfoPeer is removed from the SunToolkit and
WMouseInfoPeer is added to the WToolkit
- Screen devices initialization is added to the WMouseInfoPeer
- MONITOR_DEFAULTTONEAREST argument is
Hi.
This issue is related to windows only, but we change the shared code in
a way which can mislead someone, and the crash can be returned after
some refactoring, or when someone will call fillPointWithCoords() before
device initialization in some other place.
So it seems this code should be re
Hello,
Could you review the fix:
bug: https://bugs.openjdk.java.net/browse/JDK-8143316
webrev: http://cr.openjdk.java.net/~alexsch/8143316/webrev.00
The the native MouseInfo.fillPointWithCoords() method can access the
devices before they are initialized.
The fix moves the devices initi
