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

Nir Lisker nlisker at openjdk.java.net
Sun Jan 24 18:11:39 UTC 2021

On Sun, 24 Jan 2021 15:03:52 GMT, Matthias Bläsing <github.com+2179736+matthiasblaesing at openjdk.org> wrote:

>> Do we plan to drop support for JDK11 for OpenJFX 17? If not, we'll need to keep to the classic Switch statement, as Switch expressions were only introduced in JDK12 or 13 as a preview.
>> That said, since 17 is going to be the next LTS release, maybe the plan is to bump the dependency for OpenJFX then?
> Totally selfish request: It would be great if OpenJFX 17 would retain compatibilty with JDK 11 -- NetBeans allows including JavaFX and will retain JDK 11 compatibility for the foreseable future. I can understand, that at some point, language features will become too important to retain compatibility, but this looks dubious to me.

It was a suggestion, so Kevin can choose not to change it.

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.

While in this case the change is small and might not be worth it alone, many of the recent language changes are geared towards better readability and reduction of possible mistakes, and we will be hurting ourselves in the long run if we don't pick those up. Every PR is relatively small and doesn't require the new features it can take advantage of, but if we go this way then we will be stuck with JDK 11 until something like Valhalla comes out.


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

More information about the openjfx-dev mailing list