Activation based on cursor speed #29
Conversation
config: flick_command, flick_activation_speed; activation based on last and current motion event
|
Would you be able to describe how the feature works? Being able of explaining it here would allow us to additionally explain it in the README as well. This makes reviewing easier too. I think this is a good feature to have. I'll refrain from commenting too much until you've made the PR ready for review. Thanks already for the work! |
|
@AndreasBackx While I was formulating an answer to your question, I went into KDE to take a closer look at how it works. It turns out I was wrong about how "Screen Edges" works in KDE... To emulate their work, the following config is enough: [example]
enter_command = ["command"]
locations = ["bottom_left"]
size = 1
timeout_ms = 0Now I myself don't see the point in activating the corner by cursor speed. I think this draft can be remade to a little refactoring. At this moment events handled by pulling, which gets crazy with timeouts close to zero. That's why the minimum value 5 was made, I believe. I want to make it possible to completely remove the timeout in config, or even make it zero by default. |
Familex
changed the title
will fix #3.
At the moment it does not always triggers, can be solved by increasing the corner size.
I was thinking about the idea with several surfaces (#3 (comment)). But
Event::Enterdoes not give cursor position, which may cause poor accuracy (maybe). And it will also significantly complicate the code.I use this config for testing:
I named the activation action as
flick. Correct me if it sounds bad.Also, my changes could break activation by timeout, I haven't checked yet.