-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[Bug] Same gesture cannot be assigned to more than one action #13816
Comments
Just picked up the app for the first time in a while, and noticed this issue very quickly. It's quite annoying as swipe left used to be the default for both show answer and 'good'... I'm wondering if any of the current maintainers are using gestures? 🤔 P.s. Thanks for the workaround OP, I'd forgotten about this
|
I don't see more use cases where that would be useful besides show answer/answer X, while I can imagine a lot of misbehaviors with multiple actions for the same gesture. Would being able to separe gestures in the question and answer modes, like assigning keys, work for you? |
This may be a case where we respect the user's intelligence + intention rather than trying to put guardrails around things I can imagine a few different gesture combinations where it is legitimate to have the same gesture bound to multiple actions, but I can't think of a way to cleanly separate what we should allow and what we should not allow. (would we mark certain actions as "okay to multiple bind", if so, in what circumstances? we should maintain a list per gesture of where the multiple binding is okay? and keep that up to date? something else? ) So what if we redefine the problem as "binding the same gesture to multiple actions could be problematic", then rather than prevent it, accept as a solution user education followed by user trust. Specifically - if a user attempts to bind a gesture to an action and the gesture is already bound, open a dialog explaining "this gesture already has one or more bindings:", list the current bindings, then have a prompt that says something like "are you sure you want to bind this gesture to this action as well?" then a yes no Thoughts? |
I would agree with this, but we should fix the defaults so that users
aren't forced to experiment here
…On Thu, 31 Aug 2023, 6:24 pm Mike Hardy, ***@***.***> wrote:
This may be a case where we respect the user's intelligence + intention
rather than trying to put guardrails around things
I can imagine a few different gesture combinations where it is legitimate
to have the same gesture bound to multiple actions, but I can't think of a
way to cleanly separate what we should allow and what we should not allow.
(would we mark certain actions as "okay to multiple bind", if so, in what
circumstances? we should maintain a list per gesture of where the multiple
binding is okay? and keep that up to date? something else? )
So what if we redefine the problem as "binding the same gesture to
multiple actions could be problematic", then rather than prevent it, accept
as a solution user education followed by user trust.
Specifically - if a user attempts to bind a gesture to an action and the
gesture is already bound, open a dialog explaining "this gesture already
has one or more bindings, list the current bindings, then have a prompt
that says something like "are you sure you want to bind this gesture to
this action as well?" then a yes no
Thoughts?
—
Reply to this email directly, view it on GitHub
<#13816 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAVQBYQ4CXDRLCZAO2ZG5L3XYC3CRANCNFSM6AAAAAAXZHHJYQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Allowing user to experiment and break app is not a good idea, because in some cases they may not get any error notification at all. I see two main "conditions" here
Based on these "conditions" in this case we can divide the gestures into three categories
But the main question here is if there is a way for app to get side of the card being shown to user and take action base on :-
I see two reasons to do some development on this side
|
The way AnkiMobile handles this for taps is that the front and back side are treated as distinct, so if you want the same thing to happen on front and back, you have to set both of the gestures to do the same thing. Its swipe gestures are global though. (off topic: @timrae: saw you're working at NI these days, which is cool - my wife is into music, and uses one of their keyboards. Also, the dream you mentioned in #5805 (comment) is finally here with #14171! Hope you're well.) |
Yeah, all of that is possible |
Hello 👋, this issue has been opened for more than 3 months with no activity on it. If the issue is still here, please keep in mind that we need community support and help to fix it! Just comment something like still searching for solutions and if you found one, please open a pull request! You have 7 days until this gets closed automatically |
Hello 👋, this issue has been opened for more than 3 months with no activity on it. If the issue is still here, please keep in mind that we need community support and help to fix it! Just comment something like still searching for solutions and if you found one, please open a pull request! You have 7 days until this gets closed automatically |
Reproduction Steps
Expected Result
Gesture assigned to both actions
This used to work on last stable release. FRONT AND BACK OF A CARD CAN HAVE SAME GESTURE FOR DIFFERENT ACTION WITHOUT ANY PRACTICAL CONFLICT.
Although if a gesture is assigned to "Answer recommended (green)" it also works for "Show answer" even if it is not set for that.
So, a simple solution can be to add a note there to mention this behaviour.
Actual Result
"Already bound to show answer"
Debug info
Refer to the support page if you are unsure where to get the "debug info".
Research
Enter an [x] character to confirm the points below:
The text was updated successfully, but these errors were encountered: