1/31/2024 0 Comments Teamviewer chrome closes timeout![]() ![]() The If statement checks the errorlevel, and if set, double-taps the alt key to released the weird alt-lock. If it is NOT released, the error level is set. If the alt key is logically released, it does nothing. If it is NOT released within 3 seconds, it sets ErrorLevel to 1. It then waits for the logical state of Alt to be released, with a timeout of 3 seconds. What this script does is it fires when the alt key is PRESSED (the ~ in front) instead of released. Just posting my findings in the hops that the TV guys see this and it helps them fix the damn bug. I think maybe TV was sending an Alt keyup event when I alt-tabbed out, but somewhere inside TV, it thought alt was still down, so every time I pressed a key, it sent the alt-key combo.Īnyway. But when I pressed any key, "Aly Key Released" was popping up as if I HAD held and released Alt. My keywatch program was reporting that alt was not being held down. That should ONLY happen when I actually PRESS alt, and I was not. The edit menu opened, and autohotkey said "Alt Key Released". ![]() I could see from the menu that the alt key was stuck down. Then, I alt-tabbed out of the guest back to my local PC, and clicked back into the guest. Id press and release Alt, and I'd get the message box. By default, when using the Keyboard hooks, an Alt hotkey will not fire until AFTER the alt key is released. I used autohotkey to make a hotkey for Alt, that told me the LOGICAL status of the key (what the OS thinks the state is, regardless of actual presses or key state). Using AutoHotKey and some keystate reading tools, at no time does the software actually report that the key is being physically held down. You need to double tap alt to get out of that mode. If you tab back, and you're in stuck-Alt mode, and hit Alt once to get out of that mode, you actually just re-activate alt mode again. the state the OS knows Alt is in, and the Alt state TV thinks the guest is in. ![]() The best part? If you alt-tab back, and notice that the menu is activated by the alt, and you press and release Alt once to 'release' the menu, that does NOT release the held alt on the guest. So when you alt-tab BACK, and start to type 'edward' - E opens the Edit menu, D activates whatever Alt-D is, W closes the window (alt-W closes a lot of apps), and suddenly you're going nuts. Like as you alt-tabbed away, TV is keeping the alt key down on the guest. ![]() Not 100% of the time (I'm sure it's some odd timing issue), the guest OS keeps that Alt key stuck down. It sends an Alt keyup event.īut something breaks. When you are in a remote TV window, and press Alt, then tab, to tab back to a local window, TV sends the alt press, then as you hit tab, TV realizes, oh, you're not doing an alt-combo, so lets release the alt key. But if you press Alt-E then the menu opens. Chrome does not 'keep' the Alt key pressed. Pressing Alt puts you in this 'menu' state. It's as if you pressed and released alt, yet, the OS is unaware that you did. When alt-tabbing out of a windows based teamviewer session back to my local windows based teamviewer, very often the Alt key will get stuck 'down'. I just sat down this morning and messed with this for 2 hours. So this has been bothering me for a year. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |