> 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 incrementally with one additional commit since the last revision: Updated license header copyrights ------------- Changes: - all: https://git.openjdk.org/jfx/pull/702/files - new: https://git.openjdk.org/jfx/pull/702/files/e9dfaa75..d0d7acab Webrevs: - full: https://webrevs.openjdk.org/?repo=jfx&pr=702&range=02 - incr: https://webrevs.openjdk.org/?repo=jfx&pr=702&range=01-02 Stats: 3 lines in 3 files changed: 0 ins; 0 del; 3 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
