Sam
Sam
The documentation can definitely be updated but from my reading the code they're (both `wait_for_keypress` and `wait_for_keyevent`) returning `self.event.wait(self.time_out)` this translates to return `False` if you hit the timeout, `True`...
yeah, don't know what to tell you it returns `True` if I press the key it's waiting for and `False` if it hits the timeout, that's the expected behavior to...
Again, I'm getting the expected behavior, returns false if it hits the timeout, true if the key is pressed. What version of Autokey are you using? I'm using 0.96.09-beta.9 How...
It's intended functionality like I said, otherwise it would execute right when you hit the button which is not what most people would use it for, like many things that...
Here it is for the `qtui`; https://github.com/autokey/autokey/blob/master/lib/autokey/qtui/configwindow.py#L296 The "2000" seconds is the timeout, so you'd have to be sure to multiply in qtui or divide in gtkui so the behavior...
big changes related to this coming very soon, will be on a different commit!
It's not interesting to me but that's me, if someone else wants to figure it out and implement it and let me know what I need to do commit wise...
I've been informally using the `XDG_SESSION_TYPE` as a check in some of my WIP stuff. Please do update this if you find that is not always set to `x11` for...
@visjble If you are using the Ubuntu default screen shot preinstalled application (gnome-screenshot) you can alter your code to: `system.exec_command("gnome-screenshot -a")` Which will run the `gnome-screenshot` program with the `-a`...