K
Kajetan Chmieliński
I'm working on kiosk-like kind of application, we serve it on Linx 1010 tablets, running Windows 10.
App may work both in kiosk mode (with explorer turned off) and window mode in some places, where devices are used in various ways (basically, they need access to browser or system).
Originally application uses TabTip to allow user interaction. Since version 1703 or 1903 (when the new keyboard experience was introduced) we've had to disable it (with registry entry DisableNewKeyboardExperience). Otherwise we ended up in two keyboards displaying in window mode, new - gray one, overlapping the one we already invoke. Since new experience can't work without explorer, we went for consistency, keeping our app to invoke the keyboard.
Then we've updated to 20H2 and got surprised by the 'new experience' once again. This manifested only on our Linx tablets, on PC this wasn't observed.
DisableNewKeyboardExperience appears to have no effect now and only thing that worked was removal of TextInputHost.exe, what caused the system to stick to the old keyboard we use (surprisingly now the system uses it as well).
Since manual removal of system files is a bit hacky for an application to run properly, so my question is:
Is there any way to completely disable the new keyboard experience, like it was previously possible through the registry, without removing TextInputHost.exe program and keeping old on screen keyboard for users to navigate through the system?
Continue reading...
App may work both in kiosk mode (with explorer turned off) and window mode in some places, where devices are used in various ways (basically, they need access to browser or system).
Originally application uses TabTip to allow user interaction. Since version 1703 or 1903 (when the new keyboard experience was introduced) we've had to disable it (with registry entry DisableNewKeyboardExperience). Otherwise we ended up in two keyboards displaying in window mode, new - gray one, overlapping the one we already invoke. Since new experience can't work without explorer, we went for consistency, keeping our app to invoke the keyboard.
Then we've updated to 20H2 and got surprised by the 'new experience' once again. This manifested only on our Linx tablets, on PC this wasn't observed.
DisableNewKeyboardExperience appears to have no effect now and only thing that worked was removal of TextInputHost.exe, what caused the system to stick to the old keyboard we use (surprisingly now the system uses it as well).
Since manual removal of system files is a bit hacky for an application to run properly, so my question is:
Is there any way to completely disable the new keyboard experience, like it was previously possible through the registry, without removing TextInputHost.exe program and keeping old on screen keyboard for users to navigate through the system?
Continue reading...
