-
Notifications
You must be signed in to change notification settings - Fork 10
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
add democracy #321
base: master
Are you sure you want to change the base?
add democracy #321
Conversation
Trying to turn the input sequence back into its original form was very error-prone, e.g. it didn't manage the `hold` special case right and would instead output `a+-`. I figured it'd be best to just remember the original texts instead.
{ | ||
Sequence = input.InputSets | ||
.Select(set => set.Inputs | ||
.Select(i => i.DisplayedText).ToList()).ToList(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The old overlay relies on the input text to be regex-parseable to be recognized as a touch input and therefore displayed during execution, so this does not work for touchscreen aliases. Might be worth rethinking the wire format.
Note that in the old overlay the wire format for button sequences is shared across many places, and in particular with the anarchy_input_start
event in regards to the touch detection logic (see check_button_set_for_touchscreen
in old overlay touchscreen.js
).
No description provided.