Arrow keys autorepeating

[kkl]

I've found that when then Keyboard plugin is active, the arrow keys autorepeat. For instance, pressing the up arrow key will generate log entries of:

Keyboard.Up
Up
Emulate Keystrokes: {Up}
Autorepeat current macro: 0.6

This goes away when I disable the Keyboard plugin but, of course, I need to use it. That plugin has no configuration options. This is occurring on two different PCs and only with the arrow keys.

Anyone know of a way to disable this autorepeat behavior?

[jonib]

Anyone know of a way to disable this autorepeat behavior?

You need to remove(disable) the autorepeat action from the macro that gets triggered by the Keyboard.up event. I believe the default config in EventGhost includes a folder Keyboard Emulation, maybe the macro is there.

jonib

[kkl]

Thanks for the reply. After hunting around through a lot of _init_.py files, I thought I'd found this issue, but it seems not. When you install the Keyboard plugin, in your working *.xml file under the " <Folder Name="Keyboard Emulation" id="348">", a number of entries for the arrow keys are inserted such as:

<Macro Name="Up">
<Event Name="Up" />
<Action>
Window.SendKeys(u'{Up}')
</Action>
<Action>
EventGhost.AutoRepeat(0.59999999999999998, 0.29999999999999999, 0.01, 3.0)
</Action>
</Macro>

But I can't figure out what is generating this. The keyboard plugin itself appears to only call SetKeyboardCallback. From there, I can't track it down.

So, I tried deleting the AutoRepeat action from my *.xml. Strangely, the "Autorepeat current macro: 0.6" no longer occurs, but I still get double entries when using those keys.

Isn't this happening for others? When you click on an entry in the configuration pane of EG or even on an entry in a list of files in Windows Explorer and press the Up or Down key, do you move one line or two? I could never figure out why when I was editing text, my cursor would move back two spaces with the left key, until this problem came to light.

[jonib]

After hunting around through a lot of _init_.py files

It's somewhere in your EventGhost config (.XML file) not in any .py file.

I think you need to post your EventGhost config file, or it's impossible to know whats happening.

Edit: if you use the full Keyboard.Up event you won't get the double UP, if you only have an Up event in a macro it will trigger the macro but will not block the Up key so it gets doubled.

jonib

[kkl]

FOUND IT! In the default *.xml file that comes with the EG installation is a "Context Folder" with a subfolder of "Keyboard Emulation". When I disabled that subfolder, the double entries stopped. Jonib, thanks for weighing in.

I still don't understand why others aren't reporting this. I would assume that I'm not the only one who leaves those default entries alone and uses the Keyboard plugin.

[jonib]

FOUND IT!

Great.

I still don't understand why others aren't reporting this. I would assume that I'm not the only one who leaves those default entries alone and uses the Keyboard plugin.

Maybe most either delete or disable the default macros if they don't use them. And I think most do not use the Keyboard plugin so they don't have that problem.

jonib

[Onanation]

This has been driving me insane - I was up most of the night trying to fix it - I've had enough for today - I'll give your solution a go tomorrow. God bless you sir if it fixes the problem

[Onanation]

This is driving me insane - could you provide a little more detail kkl?

[kkl]

Disable or delete the Keyboard Emulation folder in the Context Folder.

Capture.JPG (33.99 KiB) Viewed 5487 times

[blaher]

Disable or delete the Keyboard Emulation folder in the Context Folder.

That might not be enough, because from memory the mode switching folder will re-enable the keyboard folder automatically when another program quits. You might need to disable the mode switching folder if it's there too.

[kkl]

Disable or delete the Keyboard Emulation folder in the Context Folder.

That might not be enough, because from memory the mode switching folder will re-enable the keyboard folder automatically when another program quits. You might need to disable the mode switching folder if it's there too.

Blaher, you make a very good point. If the Switch to mode: Keyboard Emulation macro gets triggered, it will re-enable the Keyboard Emulation folder. So, you're absolutely right, the Switch to mode: Keyboard Emulation macro also needs to be disabled just to be sure (or just delete, rather than disable, the Keyboard Emulation folder).

Capture2.JPG (26.22 KiB) Viewed 5470 times

[Onanation]

Thanks heaps guys - I found an even easier way - File>New

Doesn't drag in all the default stuff

that was frustrating but solved now.

Thanks again