Windows gesture typing breaks after component removals

F

FaCough

New Member
Messages
13
Reaction score
3
As the title says gesture-based typing breaks after doing my component removals. I normally use the updates, driver, registry, components, unattended, services, features and post setup parts of NTLite. Using all of the options without the comp removals results in an install with gesture-based typing functioning. With only comp removals selected it breaks. I've used NTLite since its release and Nlite for Xp before that, but this one has me a bit lost. With such a long list, well over 600 of removals, any help would be greatly appreciated!

EDIT: The short answer is you must also include "English (GB)" to retain gesture typing functionality.
 

Attachments

Last edited:
I will see if I can find where I found the name originally. I very well may be wrong. Theres not a lot of information I can find on the topic. Combined with the abundance of similarly worded apps or services, it is not an easy topic to research.

Edit: I believe this is where I picked the name up. The title and first post will be updated.
learn.microsoft.com

On-screen keyboard swipe doesn't work for all programs. - Microsoft Q&A

I can get the onscreen keyboard to swipe fine when I'm using notepad or Word, but when I try to use facebook (on chrome), either to type in the URL bar or a text field, it doesn't work. It also does not work for mIRC or scrivener, though both of those…
learn.microsoft.com
 
Last edited:
I just figured out that the issue lies in the localization section of the component removals. The hunt continues! I will share the answer if I narrow it down.
 
My suggestion would be to restore:
Code: 
<c>inputservice32 'Input Service (CTFMON) - 32 bit'</c>
<c>tabletextservice 'Table Text Service'</c>
 
Thanks for the suggestions. They've been tried, no change. However, I have tracked it down to the localization/languages section now. I noticed "Input Method Editor" under languages. As far as I can tell, it is the only entry that isn't an actual language, so I am testing that now.
 
Last edited:
Enabling the following did not help. I am going to do a sanity check with another build with all languages enabled.

<c>langime 'Input Method Editor (IME)'</c>
<c>langimejp 'Japanese (IME)'</c>
<c>langimeko 'Korean (IME)'</c>
<c>langimetc 'Chinese Traditional (IME)'</c>

EDIT: Sanity check FAILED. What was working no longer works. I have no idea why. I had two test builds with gesture typing working. Doing the same thing, the same way now fails. I am very careful with making changes. Auto import profile in NTLite is disabled so I am not sure why this happened. Enabling all of localization doesn't seem to fix it anymore.
 
Last edited:
Taking time to answer this without prodviding a full preset is time lost.
 
Not a problem! I also use a 35.5K registry file along aside of the settings tab. Not including my reg file or not using the settings section makes no difference. The TEST.xml is a stripped components only version of the actual included profile. Both result in gesture typing being non-functional. I have verified over a dozen times it is the components section. I still have no idea why I got false hope from the localization section!
 

Attachments

Last edited:
Verified 3 times, enabling the whole of the language section DOES in fact solve the issue. This is using the posted profile. Enabling localization is the only change. Back to whittling it down!
 

Attachments

  • Working.png
    Working.png
    71.2 KB
Last edited:
francis11 said:
Try enabling Touch-Screen devices in Compatibility tab.
Click to expand...
Gesture typing actually works using a mouse as well as a touchscreen. I went ahead and tested your suggestion with no change.

I believe I have it all but nailed down. I was on the right path when I suspected "Input Method Editor (IME)'". I've had many working builds with only the base IME selected in the languages section. As odd as it seems I believe there may be an order to disabling unwanted IMEs. It seems like it has to do with how I disable the secondary IMEs. When disabling the Japanese, Korean, and Chinese languages a popup shows asking to remove accompanying IME files and I am wondering if this is where it breaks. It sure seems to be. Potentially a bug perhaps? I plan on working on this until I have a concrete answer. I cannot stand it when my builds have oddities like this.
 
Last edited:
The base IME is normally required by other apps (including Accessibility), even if you don't use Asian languages. That's how alternative input methods can inject characters into the input buffer.
 
garlin said:
The base IME is normally required by other apps (including Accessibility), even if you don't use Asian languages. That's how alternative input methods can inject characters into the input buffer.
Click to expand...
Having just the base IME and English has been my goal. I've been able to achieve this several times by changing how things were selected. You can remove the secondary IMEs and languages while leaving the other languages. Gesture typing should still work. All my testing will be done on stock 25h2 until I fully figure this out.
 
I have finally found a suitable work around!!! Deselect the Language section> Select the primary IME> Unselect the secondary IMEs> Select a second language and voila functioning gesture typing! I've only tested this with English (GB) as the second language. So far, this method has worked flawlessly every time on both the language only stock 25H2 test build as well as my current project. If any project would break it, that would be this one!

Thank you to everyone that tried to help out. It is greatly appreciated. Sorry for the sloppy post. I haven't posted to a forum in 15 plus years. An extreme case of dyslexia doesn't help lol.
 
Just a quick and final update. You do not need to have any of the input method editors enabled. You do however need to have English (GB) selected for gesture typing to function. Simply having a second language has no effect.
 
You must log in or register to reply here.
Back
Top