> When processing a `WM_CHAR` event on an OEM key (punctuation, symbol, dead > key) the glass code will dynamically query the key's unshifted character to > determine the Java code to assign to it. This is necessary since the > relationship between OEM key codes and the characters they generate varies > from layout to layout. > > The Robot implementation was consulting a table which assumed a fixed > relationship between Java codes and Windows key codes even for the OEM keys. > The table was also missing entries for any Java code not on a US QWERTY > layout, like PLUS. > > In this PR if we don't find the Java code in the table or if it maps to an > OEM key (which may be wrong) we sweep through all the OEM keys looking for > the matching Java code.
Martin Fox has updated the pull request with a new target base due to a merge or a rebase. The incremental webrev excludes the unrelated changes brought in by the merge/rebase. The pull request contains five additional commits since the last revision: - Coding style consistency - Merge remote-tracking branch 'upstream/master' into winrobot - Updated license header copyrights - A Robot now correctly handles KeyCodes that aren't in the current layout - Robot now targets punctuation and symbol keys reliably ------------- Changes: - all: https://git.openjdk.org/jfx/pull/702/files - new: https://git.openjdk.org/jfx/pull/702/files/d0d7acab..d6063597 Webrevs: - full: https://webrevs.openjdk.org/?repo=jfx&pr=702&range=03 - incr: https://webrevs.openjdk.org/?repo=jfx&pr=702&range=02-03 Stats: 1319721 lines in 14952 files changed: 713537 ins; 422213 del; 183971 mod Patch: https://git.openjdk.org/jfx/pull/702.diff Fetch: git fetch https://git.openjdk.org/jfx.git pull/702/head:pull/702 PR: https://git.openjdk.org/jfx/pull/702
