-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Separate threshold/interval for keypress commands #3
Comments
Thanks for your suggestion! Here's what I'm thinking right now about adding features in the future. I will not change the syntax of threshold/interval for swipe because we want to be compatible. Instead, we implement the following two
swipe:
3:
left:
command: echo "oneshot event"
scroll: # for realtime event
3:
left:
command: echo "realtime(100 events/sec)"
throttle:
wait: 100
command: echo "event(10 events/sec)"
|
I'm sorry I think I'm not understanding completely. I meant my suggestion as an addition. So no existing feature would be changed. Just more granular controls for threshold and interval. So instead of current example of priorities from README:
It would be:
To me it made visual sense. That said, part of the reason for writing this now is that I am not educated enough to understand your suggestion. (But I don't need to understand. I trust that you know what you're doing, so no need to waste your time on explanations, unless you want to). Also I wanted to mention, that (even though I barely know anything about architecture) I think there is such a thing as overdoing backwards compatibility. I found using Fastlane really unpleasant because of all the legacy weirdness in it. Very little consistency and poor naming and things awkwardly glued onto other things all around. But nobody wants to break anything - even thought that's what major releases are for in semver. Not saying there's a problem here, but just something to keep in mind maybe. |
I'm sorry for not being able to explain it well.
Is it https://github.com/fastlane/fastlane? I have never used it.
Does it mean following ?
My English is not that good. But I want to write better software, so I want to understand what you're saying. |
I don't know much about common/popular opinion about fastlane. I only have my personal subjective uneducated opinion. With the sentence...
... I meant that - I think a situation can exist in which other aspects of software are neglected horribly in order to remain backwards compatible. I mean other aspect like:
|
Thank you for your advice. |
Thanks for your lovely software. |
BTW, Fusuma v2 has been released. iberianpig/fusuma#224
These features should cover your use case. swipe:
3:
right:
update:
keypress:
LEFTCTRL:
command: "xdotool key --clearmodifiers XF86AudioRaiseVolume"
left:
update:
keypress:
LEFTCTRL:
command: "xdotool key --clearmodifiers XF86AudioLowerVolume"
---
context:
application: Google-chrome
swipe:
3:
right:
command: "xdotool click 9" # History forward
left:
command: "xdotool click 8" # History back |
It would be nice extra feature to be able to adjust the threshold and interval separately for each of the keypress commands.
So that e.g. without keypress you use one set of interval and threshold and for keypress LEFTCTRL you use another set of interval and threshold and another one for LEFTMETA.
Hoped this would work like that:
Actually interval/threshold only work if I move them to the same indentation level as keypress, in which case they also apply to the history back and history forwards (which is unwanted in this case).
The text was updated successfully, but these errors were encountered: