-
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
Mouse interaction alerts cannot run on endDrag #233
Comments
From that comment:
|
I have potentially fixed this with two items.
Please review, and let me know if you want to talk through this. This is only on master right now, not on dev.15 |
This sounds pretty good. |
@Matthew-Moore240 and @terracoda discussed, and we feel it would be better if there was some movement (some interaction) before you get move down to rub harder. That said, if movement and space simultaneously are hard to detect we can live with it as is. The main idea of the response is that it indicates unproductive rubbing. Having it fire with just air space seems a little extra directive, but not terrible. |
@terracoda @zepumph and @Matthew-Moore240 Reviewed this together and decided to leave it as is. Closing. |
30ad85b doesn't seem to cut it to me. I was reviewing this code over in #242 (comment) and think it needs to be reworked. It will be done over in #253 where Utterance timing variables will be used instead of in house counting. |
From #231 (comment), we need to update FrictionDragListener so that we don't wait until endDrag to alert. Let's prototype with trying to do it every X drags. Otherwise we may just have to use the Utterance timing variables for this, but I don't see it as a good fit.
The text was updated successfully, but these errors were encountered: