Re: RFR: 8089373: Translation from character to key code is not sufficient [v2]

2024-02-19 Thread Michael Strauß
On Fri, 9 Feb 2024 03:37:17 GMT, Martin Fox wrote: >> On Windows a common shortcut like Ctrl+'+' could only be invoked from the >> main keyboard and not the numeric keypad. Toolkit.getKeyCodeForChar did not >> have enough context to know whether it should return a result from the main >> keybo

Re: RFR: 8089373: Translation from character to key code is not sufficient [v2]

2024-02-09 Thread Andy Goryachev
On Fri, 9 Feb 2024 03:37:17 GMT, Martin Fox wrote: >> On Windows a common shortcut like Ctrl+'+' could only be invoked from the >> main keyboard and not the numeric keypad. Toolkit.getKeyCodeForChar did not >> have enough context to know whether it should return a result from the main >> keybo

Re: RFR: 8089373: Translation from character to key code is not sufficient [v2]

2024-02-09 Thread Martin Fox
On Thu, 8 Feb 2024 19:26:42 GMT, Andy Goryachev wrote: >> 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 seven additional >> commits

Re: RFR: 8089373: Translation from character to key code is not sufficient [v2]

2024-02-09 Thread Martin Fox
On Thu, 8 Feb 2024 19:20:32 GMT, Andy Goryachev wrote: >> 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 seven additional >> commits

Re: RFR: 8089373: Translation from character to key code is not sufficient [v2]

2024-02-08 Thread Martin Fox
> On Windows a common shortcut like Ctrl+'+' could only be invoked from the > main keyboard and not the numeric keypad. Toolkit.getKeyCodeForChar did not > have enough context to know whether it should return a result from the main > keyboard or the keypad. > > This PR alters getKeyCodeForChar

Re: RFR: 8089373: Translation from character to key code is not sufficient

2024-02-08 Thread Andy Goryachev
On Fri, 17 Nov 2023 20:05:09 GMT, Martin Fox wrote: > On Windows a common shortcut like Ctrl+'+' could only be invoked from the > main keyboard and not the numeric keypad. Toolkit.getKeyCodeForChar did not > have enough context to know whether it should return a result from the main > keyboard

Re: RFR: 8089373: Translation from character to key code is not sufficient

2024-01-29 Thread Andy Goryachev
On Fri, 17 Nov 2023 20:05:09 GMT, Martin Fox wrote: > On Windows a common shortcut like Ctrl+'+' could only be invoked from the > main keyboard and not the numeric keypad. Toolkit.getKeyCodeForChar did not > have enough context to know whether it should return a result from the main > keyboard

Re: RFR: 8089373: Translation from character to key code is not sufficient

2024-01-17 Thread Martin Fox
On Fri, 17 Nov 2023 20:05:09 GMT, Martin Fox wrote: > On Windows a common shortcut like Ctrl+'+' could only be invoked from the > main keyboard and not the numeric keypad. Toolkit.getKeyCodeForChar did not > have enough context to know whether it should return a result from the main > keyboard

Re: RFR: 8089373: Translation from character to key code is not sufficient

2023-12-20 Thread Martin Fox
On Fri, 17 Nov 2023 20:05:09 GMT, Martin Fox wrote: > On Windows a common shortcut like Ctrl+'+' could only be invoked from the > main keyboard and not the numeric keypad. Toolkit.getKeyCodeForChar did not > have enough context to know whether it should return a result from the main > keyboard

RFR: 8089373: Translation from character to key code is not sufficient

2023-11-17 Thread Martin Fox
On Windows a common shortcut like Ctrl+'+' could only be invoked from the main keyboard and not the numeric keypad. Toolkit.getKeyCodeForChar did not have enough context to know whether it should return a result from the main keyboard or the keypad. This PR alters getKeyCodeForChar to pass in t

Re: RFR: 8089373: Translation from character to key code is not sufficient [v3]

2023-07-12 Thread Martin Fox
On Mon, 10 Jul 2023 16:41:47 GMT, Andy Goryachev wrote: >> At this point I don't have a strong opinion on whether this field is private >> or not. Originally I wanted it to be private because I thought of it as >> "whatever magic value makes KeyCharacterCombinations work" and was concerned >>

Re: RFR: 8089373: Translation from character to key code is not sufficient [v3]

2023-07-10 Thread Andy Goryachev
On Tue, 9 May 2023 17:34:23 GMT, Martin Fox wrote: >> modules/javafx.graphics/src/main/java/javafx/scene/input/KeyEvent.java line >> 388: >> >>> 386: * The hardware key code which is private to the implementation. >>> 387: */ >>> 388: private int hardwareCode; >> >> Does it need

Re: RFR: 8089373: Translation from character to key code is not sufficient [v3]

2023-06-09 Thread Martin Fox
On Thu, 11 May 2023 02:46:47 GMT, Martin Fox wrote: >> Note: the Java-side changes in this PR are also in #694 which fixes the same >> issue (and more) on Linux. Unfortunately the Linux Robot code is not working >> making it difficult to test on that platform (see #718). >> >> KeyCharacterComb

Re: RFR: 8089373: Translation from character to key code is not sufficient [v3]

2023-06-09 Thread Andy Goryachev
On Fri, 9 Jun 2023 18:25:39 GMT, Martin Fox wrote: > App developers have a hard time sorting this out There was a discussion on the mailing list about adding a doc/ folder with markdown informational notes. (Build instructions and snapping rules were the prime candidates for such notes). If

Re: RFR: 8089373: Translation from character to key code is not sufficient [v3]

2023-06-09 Thread Martin Fox
On Thu, 11 May 2023 02:46:47 GMT, Martin Fox wrote: >> Note: the Java-side changes in this PR are also in #694 which fixes the same >> issue (and more) on Linux. Unfortunately the Linux Robot code is not working >> making it difficult to test on that platform (see #718). >> >> KeyCharacterComb

Re: RFR: 8089373: Translation from character to key code is not sufficient [v3]

2023-05-10 Thread Martin Fox
> Note: the Java-side changes in this PR are also in #694 which fixes the same > issue (and more) on Linux. Unfortunately the Linux Robot code is not working > making it difficult to test on that platform (see #718). > > KeyCharacterCombinations allow the specification of accelerators based on

Re: RFR: 8089373: Translation from character to key code is not sufficient

2023-05-10 Thread Martin Fox
On Fri, 5 May 2023 20:20:02 GMT, John Hendrikx wrote: > > I'm not quite sold on having `notifyKey` and `notifyKeyEx` be two separate > > methods. Why not just have one? Not changing the existing call sites > > doesn't seem to be a sufficient reason to expand the toolkit API surface. > > I also

Re: RFR: 8089373: Translation from character to key code is not sufficient [v2]

2023-05-10 Thread Martin Fox
> Note: the Java-side changes in this PR are also in #694 which fixes the same > issue (and more) on Linux. Unfortunately the Linux Robot code is not working > making it difficult to test on that platform (see #718). > > KeyCharacterCombinations allow the specification of accelerators based on

Re: RFR: 8089373: Translation from character to key code is not sufficient

2023-05-10 Thread John Hendrikx
On Tue, 9 May 2023 20:38:35 GMT, Martin Fox wrote: >> modules/javafx.graphics/src/main/native-glass/win/KeyTable.cpp line 366: >> >>> 364: UINT keyChar = ::MapVirtualKeyEx(UINT(hardwareCode), 2, >>> layout); >>> 365: // Filter out dead keys >>> 366: BOOL isDead = (keyCha

Re: RFR: 8089373: Translation from character to key code is not sufficient

2023-05-09 Thread Martin Fox
On Fri, 5 May 2023 20:04:12 GMT, John Hendrikx wrote: >> Note: the Java-side changes in this PR are also in #694 which fixes the same >> issue (and more) on Linux. Unfortunately the Linux Robot code is not working >> making it difficult to test on that platform (see #718). >> >> KeyCharacterCo

Re: RFR: 8089373: Translation from character to key code is not sufficient

2023-05-09 Thread Martin Fox
On Fri, 5 May 2023 20:25:23 GMT, John Hendrikx wrote: >> modules/javafx.graphics/src/main/java/com/sun/javafx/tk/Toolkit.java line >> 709: >> >>> 707: * The default implementation bridges into the existing >>> getKeyCodeForChar call. >>> 708: */ >>> 709: public boolean getKeyCanG

Re: RFR: 8089373: Translation from character to key code is not sufficient

2023-05-09 Thread Martin Fox
On Fri, 5 May 2023 20:00:55 GMT, John Hendrikx wrote: >> Note: the Java-side changes in this PR are also in #694 which fixes the same >> issue (and more) on Linux. Unfortunately the Linux Robot code is not working >> making it difficult to test on that platform (see #718). >> >> KeyCharacterCo

Re: RFR: 8089373: Translation from character to key code is not sufficient

2023-05-05 Thread John Hendrikx
On Fri, 5 May 2023 19:45:53 GMT, John Hendrikx wrote: >> Note: the Java-side changes in this PR are also in #694 which fixes the same >> issue (and more) on Linux. Unfortunately the Linux Robot code is not working >> making it difficult to test on that platform (see #718). >> >> KeyCharacterCo

Re: RFR: 8089373: Translation from character to key code is not sufficient

2023-05-05 Thread John Hendrikx
On Fri, 5 May 2023 19:38:36 GMT, Martin Fox wrote: > I'm not quite sold on having `notifyKey` and `notifyKeyEx` be two separate > methods. Why not just have one? Not changing the existing call sites doesn't > seem to be a sufficient reason to expand the toolkit API surface. I also think it isn

Re: RFR: 8089373: Translation from character to key code is not sufficient

2023-05-05 Thread John Hendrikx
On Thu, 4 May 2023 17:18:21 GMT, Martin Fox wrote: > Note: the Java-side changes in this PR are also in #694 which fixes the same > issue (and more) on Linux. Unfortunately the Linux Robot code is not working > making it difficult to test on that platform (see #718). > > KeyCharacterCombinatio

Re: RFR: 8089373: Translation from character to key code is not sufficient

2023-05-05 Thread Martin Fox
On Fri, 5 May 2023 16:35:38 GMT, Michael Strauß wrote: > I'm not quite sold on having `notifyKey` and `notifyKeyEx` be two separate > methods. Why not just have one? Not changing the existing call sites doesn't > seem to be a sufficient reason to expand the toolkit API surface. The long term g

Re: RFR: 8089373: Translation from character to key code is not sufficient

2023-05-05 Thread Kevin Rushforth
On Thu, 4 May 2023 17:18:21 GMT, Martin Fox wrote: > Note: the Java-side changes in this PR are also in #694 which fixes the same > issue (and more) on Linux. Unfortunately the Linux Robot code is not working > making it difficult to test on that platform (see #718). > > KeyCharacterCombinatio

Re: RFR: 8089373: Translation from character to key code is not sufficient

2023-05-05 Thread Michael Strauß
On Thu, 4 May 2023 17:18:21 GMT, Martin Fox wrote: > Note: the Java-side changes in this PR are also in #694 which fixes the same > issue (and more) on Linux. Unfortunately the Linux Robot code is not working > making it difficult to test on that platform (see #718). > > KeyCharacterCombinatio

RFR: 8089373: Translation from character to key code is not sufficient

2023-05-04 Thread Martin Fox
Note: the Java-side changes in this PR are also in #694 which fixes the same issue (and more) on Linux. Unfortunately the Linux Robot code is not working making it difficult to test on that platform (see #718). KeyCharacterCombinations allow the specification of accelerators based on characters