RFR: 8259680: Need API to query states of CAPS LOCK and NUM LOCK keys

Kevin Rushforth kcr at openjdk.java.net
Mon Jan 25 15:09:41 UTC 2021

On Mon, 25 Jan 2021 14:50:58 GMT, Kevin Rushforth <kcr at openjdk.org> wrote:

>>> Formally, OpenJFX N supports JDK N-1, so for 17 we should be able to use features from 16. It was decided a while back not to force-fail on older JDK versions and let it evolve naturally.
>> That's the bit of information I was missing, thanks.
> Bumping the minimum version of the JDK that is required to run the current version of JavaFX requires prior discussion on the openjfx-dev mailing list and a separate JBS Enhancement, like we did when we bumped the minimum to JDK 11 with [JDK-8209966](https://bugs.openjdk.java.net/browse/JDK-8209966) + [JDK-8210093](https://bugs.openjdk.java.net/browse/JDK-8210093). We wouldn't do it in connection with a bug fix such as this.
> Having said that, I was already thinking that JavaFX 17 is a good time to consider bumping the minimum to allow using some of the newer JDK language features, so I'll start that discussion on the list soon.

> Also, do we use a space after switch? I see many instances both with and without in the current source.

According to the coding guidelines, there should always be a space after operators such as `if`, `for`, `while`, and `switch` (to distinguish them from method calls). If there are occurrences of `switch(expr)` without the space, they are not following the guidelines.


PR: https://git.openjdk.java.net/jfx/pull/385

More information about the openjfx-dev mailing list