-
Notifications
You must be signed in to change notification settings - Fork 6
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
Keyboard Interaction: Measure Distance Ruler - Combining Release and Grab strings #205
Comments
@zepumph, actually, I think the double "Release" was just a timing glitch. I think only one "Release" is being spoken on the actual release interaction, and there is an erroneous "Release" string being added to the grab interaction response. |
I think that #203 (comment) actually applies to this issue:
|
Yes I get this sometimes. It is not because of any of the alerts. I think it has to do with the kinks we are still working out in successfully grabbing/releasing the ruler each time the user intends to. (like #201 and #210). I would like to try to sort out at least #210 and then see if this sounds any better. I was having trouble when it felt like I wasn't able to grab it successfully each time, and then after trying a few times I was then able to grab it (if that sounds confusing it is because I'm confused). I'll look in on this after #210. |
@zepumph, I seem to get "Release." on grab, and "Grabbed." on release in addition to the correct strings. It seems it could be related to yours and @jessegreenberg comment in #205 (comment) Good luck. (corrected typo) |
@terracoda are you still getting this bug? I know @jessegreenberg has done a lot of work on the grab/drag interaction in the last month. |
Good question, I'll check. I am getting correct "Grabbed" and "Released." And at the right times! I am closing this issues. |
In #141 the Grab alert was corrected.
However, recent changes seem to have combined "Released" and "Grabbed" strings into the grab response.
@zepumph, could you have a look. It might just be a copy/paste error.
The text was updated successfully, but these errors were encountered: