autokey | desktop automation utility

the following solution only works with root rights:

The github.com/micmonay/keybd_event package provides an API for simulating keystrokes cross-platform, I.e on Linux, MacOS and Windows.

The API does not however provide a way of mapping strings to a sequence of keypresses. That you will have to implement yourself or alternatively, if you want us to help, describe how you would like the strings to be mapped to keypresses.

https://github.com/autokey/autokey/blob/fc7c6b90f3f28a57ad256829ef2b69e3be5148d2/lib/autokey/scripting.py#L1242

engine.run_script("")

ought to do the trick

"Description" in this context is generally the name of the script in the side bar in the AutoKey interface. If you open up the .json file for the script you can see it for sure, but it will be the name displayed in the side bar unless you have duplicate names for scripts in the same folder or some other edge scenario

These problems have not disappeared for a few days as a result of the following changes:

The solution described above uses the clipboard and keyboard together with Linux and Windows (Wine) conveyed via two scripting languages.

Apps:
clipboard ⇄ AutKey ⇄ AutoHotKey ⇄ Lintalist

operating systems:
clipboard ⇄ Kubuntu ⇄ WineHQ ¹

Errors are more common in non-closed systems. Therefore, for example, such errors are typical (still open problem at 2020:11:12 in autokey):

"Hotkeys get lost when triggered frequently"

1. change from autokey-gtk to autokey-qt for systems using a Qt-based desktop environment such as KDE Plasma, Lumina, etc. For that there are different possibilities (github: install using pip3). I've used i used:

You need to add json['hotkey'] reference before:

TL;DR: Not directly with our API.

The AutoKey API talks directly to the current active window. So, sending events targeted at the desktop (DTE) will only work if the current active window recognizes them as such and either forwards them to the DTE or emulates what they do.

However, since AutoKey scripts are written in full Python 3, if you can figure out how to do it yourself in Python, AutoKey can run it for you. And, if some other solution is available, you can run it from within an AutoKey script using the subprocess module.

it moves the mouse relatively using autopilot.input.

to install:

sudo apt-get install python3-autopilot

There's no reason to childByAutoId within peoplWhoLikeMe in this use case, and it further complicates the rules.

You know the specific data you want to store, so just store that data with a placeholder for the value.

In other words, I assume you're storing users UID's so your structure would be

There are quite some issues with the example. I'll point out the ones that jump out to me below:

1. These rules