> Currently on macOS when mouseMove is given an offscreen coordinate to move > the mouse to, mouseMove will physically clamp to the edge of the screen, but > if you try to grab the mouse location immediately after by using > MouseInfo.getPointerInfo().getLocation() you will get the value of the > offscreen point. > > Windows and linux do this clamping and coordinate handling for us, but new > distributions may not necessarily handle clamping the same way, so Robot > should be checking for clamping rather than delegating it to native. > > This fix updates shared code to cache the screen bounds and adds a check to > not exceed the bounds in mouseMove. The caching is done in the Robot > constructor, so if the screen bounds changes the constructor must be called > again to update to the new bounds.
Alisen Chung has updated the pull request incrementally with one additional commit since the last revision: use absolute distance to choose correct screen for offscreen clamping ------------- Changes: - all: https://git.openjdk.org/jdk/pull/22781/files - new: https://git.openjdk.org/jdk/pull/22781/files/5cd1e6a7..82044442 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=22781&range=11 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=22781&range=10-11 Stats: 27 lines in 1 file changed: 6 ins; 12 del; 9 mod Patch: https://git.openjdk.org/jdk/pull/22781.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22781/head:pull/22781 PR: https://git.openjdk.org/jdk/pull/22781
