ADDITIONAL SYSTEM INFORMATION :
Windows 10 on Surface book (detached and attached)
JavaFX 15.0.2
Java 11.0.9
A DESCRIPTION OF THE PROBLEM :
With the new landscape of desktop class devices getting touch screens as well as different orientations and positions which enable and disable the physical keyboard JavaFX should detect the presence of a physical keyboard and show the native (or sw) keyboard automatically instead of requiring the opt in by D props prior to launching. The current approach makes it extremely difficult to write an application which works well on devices which support these various detached modes since the end user needs to determine ahead of time if they want to enable the OSK or not and then must add these properties themselves or as a developer a one-way speed bump of some kind needs to be created in order to give the user an option. Also, this means that from that point on they are locked into their choice and a complete relaunch of the application is required if they change their configuration.
Another reason this is tough: the current software keyboard (FXVK) is EXTREMELY difficult to work with and show/hide programmatically so adding a runtime option to use this keyboard is essentially out of the question. This keyboard isn't ideal either since it has location issues on multiple monitor configurations with mixed resolutions.
Windows 10 on Surface book (detached and attached)
JavaFX 15.0.2
Java 11.0.9
A DESCRIPTION OF THE PROBLEM :
With the new landscape of desktop class devices getting touch screens as well as different orientations and positions which enable and disable the physical keyboard JavaFX should detect the presence of a physical keyboard and show the native (or sw) keyboard automatically instead of requiring the opt in by D props prior to launching. The current approach makes it extremely difficult to write an application which works well on devices which support these various detached modes since the end user needs to determine ahead of time if they want to enable the OSK or not and then must add these properties themselves or as a developer a one-way speed bump of some kind needs to be created in order to give the user an option. Also, this means that from that point on they are locked into their choice and a complete relaunch of the application is required if they change their configuration.
Another reason this is tough: the current software keyboard (FXVK) is EXTREMELY difficult to work with and show/hide programmatically so adding a runtime option to use this keyboard is essentially out of the question. This keyboard isn't ideal either since it has location issues on multiple monitor configurations with mixed resolutions.
- relates to
-
JDK-8090530 Native Windows virtual keyboard should be supported
- Open
-
JDK-8263830 Provide virtual keyboard support on desktop platforms
- Open