Hi!
Thanks for concept which potentially gives much better on-screen keyboard.
However provided method to replace OSK is unreliable because of a lot of issues:
- admin elevate doesn't work. Scripts simply relaunch itself in endless loop. So all you see is endless re-spawning cmd window. Solution: launch cmd as admin and remove the part of script checking and re-launching the script.
- Current Aya Neo registry has DWORD value starting with 0x86xxxxx, so this query:
reg Query "HKLM\Hardware\Description\System\CentralProcessor\0" | find /i "x86" always true and thus choose 32bit framework instead of 64bit and of course later execution go wrong way. solution: add unconditional line set FrameWork=Framework64
- registry change
reg add HKLM\SOFTWARE\Microsoft\TabletTip\1.7 /t REG_DWORD /v EnableDesktopModeAutoInvoke /d 1 /f doesn't go to original place. It goes to some process-specific branch and thus doesn't work system wide. Solution: open regedit and add this manually.
- osk.exe doesn't exists in system-wide \windows\system32\ folder. it exists in process specific substitution folder visible for process launching osk.exe. So replaced osk.exe in script isn't used by Aya Neo button and original osk.exe is launched instead. Solution: launch original osk.exe, then through task manager open containing folder, then through manipulation of taking ownership, adding permission, fight with windows antivirus blocks, replace osk.exe there manually.
Now it works ;) However button it seems bouncing a lot, so when i press it, it often open and immediately closes the keyboard. It's better to remove closing the keyboard by button. So button will only open the keyboard. Closing can be accomplished by pressing X on top right corner. Or may be add timeout to exclude bouncing.
I don't know which process bound to that hardware button. May be it would be better to redirect the button to TabTipProxy explicitly without using osk.exe, so at least it won't trigger windows protection.
Hi!
Thanks for concept which potentially gives much better on-screen keyboard.
However provided method to replace OSK is unreliable because of a lot of issues:
reg Query "HKLM\Hardware\Description\System\CentralProcessor\0" | find /i "x86"always true and thus choose 32bit framework instead of 64bit and of course later execution go wrong way. solution: add unconditional lineset FrameWork=Framework64reg add HKLM\SOFTWARE\Microsoft\TabletTip\1.7 /t REG_DWORD /v EnableDesktopModeAutoInvoke /d 1 /fdoesn't go to original place. It goes to some process-specific branch and thus doesn't work system wide. Solution: open regedit and add this manually.Now it works ;) However button it seems bouncing a lot, so when i press it, it often open and immediately closes the keyboard. It's better to remove closing the keyboard by button. So button will only open the keyboard. Closing can be accomplished by pressing
Xon top right corner. Or may be add timeout to exclude bouncing.I don't know which process bound to that hardware button. May be it would be better to redirect the button to TabTipProxy explicitly without using osk.exe, so at least it won't trigger windows protection.