Keystrokes are intercepted in Windows 10 1809
Quickly OCR part of the screen and save resulting text to clipboard
Brought to you by:
cb4960
Menu
▾
▴
#163 Keystrokes are intercepted in Windows 10 1809
I have 4.6. laded n Windows 10 1809.
I can capture on Win+Q, though I usually have to click this combo a few times before the blue rectangle starts.
The issue is that relatively quickly it starts intercepting keys, most often the o and other seemingly random letters/numbers. To be able to input properly at my keyboard again I need to kill the program. What is going on?
Related
I want to use this software but because it stops me typing by swallowing letters I keep having to turn it off., e.g. there will be no "o" when I type due to this being loaded. There is nowhere else to ask for help that I can see. Please, can someone advise me?
Last edit: boardtc 2021-03-15
Does nobody else have this issue? I want to use this all the time but have to stop and start each time I use it because of this issue,
I have exactly the same problem. In fact, I had to stop, reboot my system and continue in the midst of posting this reply as a result of an experiment. ** It's making it very difficult to use Capture2Text at all.** I noticed that the Capture2Text settings were periodically switching the OCR language n to Japanese and thought that might be the problem. So I took care to prevent accidental Capture2Text-induced language switches by use of partial hotkey sequences, and it seems to be remaining "English" more reliably now. I have looked around in all the places Windows might be automatically switching language contexts and disabled or trained them all towards English. One question for @boardtc: are you using the "replace" facility? Two events happened around the same time: some windows updates and my introduction of the "replace" facility into my workflow. I suppose I ought to back out the entries in that table to see if the problem goes away. If it does, I'll report back here. If I haven't assume that it didn't. Meanwhile, I'm hoping someone on the dev and support team can reproduce this problem and either give us configuration pointers or an update.
I've solved the problem - I changed all of the Hotkeys mappings to "Unmapped", and the problem went away. The problem, I believe, was provoked when I unchecked the boxes next to "Win", "Alt", and so on, to avoid having Capture2Text override other useful keys. In effect I had left those functional mappings as hot-key tied to the keystrokes themselves instead. The breakthrough came the moment I noticed status words popping up on my screen every time I pressed "o", cycling through "vertical", "horizontal", and "auto" (or some such). In any case I unmapped all these functions (I can re-map them if and when they are useful) and lo! behold! I can now type while Capture2Text is running and not experience those annoying disappearing keystrokes.
Last edit: Roger Neyman 2021-05-17
Thank for your contributions Roger, it's a relief that someone sees this crippling issue!
I tried removing all the hotkey mappings except WinKey+q but the issue does not correct for me. Even after a restart of Capture2Text.
That said this hotkey dialog is at the heart of the problem, as I did further digging and the keys swallowed are w, e, o, r,s, 1,2,3 - all the default hotkeys.
Futhermore, if you assign a key to the whitelist toggle, e.g. n, this also gets swallowed.
Please can someone look at this bug?
Updated for Alt+q typo
Last edit: boardtc 2021-05-18
(( ed note: I wrote this as an email post before I saw the screenshot above. -- please also see my next post reacting to it. ))
double check. those are the very hotkeys that are mapped by default. dont
just uncheck the boxes, but set the dropdown list to unmapped. also make
sure you don't have a hidden copy running, say, at system startup... after
you change the settings exit and restart and check them again
On Mon, May 17, 2021, 02:03 boardtc tomcorcoran@users.sourceforge.net
wrote:
Related
Tickets: #163
Last edit: Roger Neyman 2021-05-17
Just as I thought. The configuration shown remaps the key combination "Win-Q" (Not Alt-Q) and all the keystrokes "R" "E" "W" "S" "1" "2" "3" "O" to serving Capture2Text functions. To unmap a combination (instead of just unchecking the four modifier keys (Ctrl Shift Alt Win) you need to click on the down arrow to the right of the letter and select
<Unmapped>. If there's a bug it is that the dialog box doesn't make this point clear. The only thing accomplished by simply unchecking the four boxes is to change the mapping from an modified letter to the letter itself - it is still remapped to be a function instead of a keystroke.Last edit: Roger Neyman 2021-05-17
**My suggestion to the designer/maintainers of Capture2Text is two fold. **
(1) Add a short text message to this dialog (e.g.)
"To unmap a function select
<Unmapped>from drop-down list"(2) Do not allow the user de-select all of the modifier keys. When they do so, reenable the last one de-selected and pop up a message saying you must select at least one. In short, the effect would be that only modified keystrokes can be remapped. This is only a minor limitation, but a reasonable one. It will force an intitive user to look for a different mechanism to unmap a function or (as they may look at it) to un-remap a keystroke they want to use elsewhere.
Last edit: Roger Neyman 2021-05-18
Added note to the Hotkeys settings page regarding the proper method to disable hotkeys per your suggestion.
perfect solution, cb4960. Thanks. I, for one, would be happy to see this support item closed.
Last edit: Roger Neyman 2022-03-25
Perfect. Thanks, cb4960. I, for one, would be happy to see this support
item closed.
For the record boardtc, it isn't really a work-around.
-. --... .-. .--. -.
-. --... .-. .--. -.*
On Fri, Mar 18, 2022 at 7:01 PM cb4960 cb4960@users.sourceforge.net wrote:
Related
Tickets: #163
Thanks for the < unmapped > tip, that works!!
This is most definitely a bug surely? If capture2text is running I can't use 8 keys on my keyboard without this workaround!
Last edit: boardtc 2021-05-18
No, not really a bug in the product at all. Just a bug in the documentation, at most. Now fixed.
This is a very useful tool.