-
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
Tick mark description says "around" when it is "on" #279
Comments
@zepumph, I found spot where the incorrect "around" can happen without ratio locked. When I have 1:3 and have the Tick Mark Range set to 0 to 30, the first tick mark seems to always be described as "around first Tick Mark". Screenshot of Responses in A11y View Maybe some kind of rounding error? |
Yes, it is a rounding error. I can reproduce it consistently by moving the consequent, because then the model has to recompute what the antecedent should be:
I feel like this has something to do with #243. Perhaps I'm clamping too early in a case, and then it isn't able to round up to 3. |
This has been fixed by 47ef113. @terracoda can you please confirm and feel free to close. |
I did a fresh pull. cleared history, and cleared caches. Steps to reproduce:
Adding note - you have to use the shift key to get the left hand on tick mark 1. I can't actually get the left hand to tick mark 1 unless the right hand is on tick mark 3. |
This happens with sliders and the both hands interactions. |
back over to you @zepumph. |
Oh sorry, I lied. I didn't read the "around" in the previous post :-P |
I think it may only be an issue with range 0 to 30. |
@terracoda and I discussed this further today, and we see that this is because of using a shift keyboard step of 1/10 of an original tick mark, even when the range changes to 1/30. In this case, every tick mark that isn't divisible by 3 will be "around" because of the underlying math, not a rounding error. Over to @terracoda. |
Above discussion moved to #298, @terracoda please review that the original bug in the first comment is fixed. |
@zepumph, yep this rounding issue is resolved. The left hand is now "on" the tick mark. Closing. |
Ok, after a reset and then explore only with the keyboard on the 0 to 30 grid, I am always on a tick mark or on a half tick mark. When I start using the mouse to get visually aligned with a visual tick mark, I get "around". When I start using the keyboard again, the grid snaps back to being on a tick mark or on a half tick mark. I think the smaller grid value that we discussed yesterday has improved the situation. In fact, when I use the mouse, I can more easily get "around" now on any grid. That might have been the case before - not sure since I didn't test with the mouse much. Now, whenever I switch back to using the keyboard, I seem to snap back onto "on" a tick mark or "on" a half tick mark. I'm thinking things are ok now. I'd like to see, in the description, where we transition from "around" a tick mark to "around" a half tick mark. Sometime this might seem confusing, but maybe I am trying to be too precises in an imprecise environment. |
oops, wrong issue. |
From #245 (comment), @terracoda found a bug while reviewing that issue.
Here are her posts describing it over there:
With ratio locked, it seems when the left hand is visually "on a tick mark", it described as being "around" to tick mark.
Here's 2 screen shots. Not sure if this is directly related to this issue, but since I am testing this issue, I just need to post it here before I lose my train of thought:
Double checking with Lock Ratio unchecked.
Ok, this seems to happen only with Lock Ratio checked.
I can start out with Both Hands at 1:3 with each on the correct tick mark, but by the time the Left Hand gets to Tick Mark 2, the descriptions says "around tick mark 2" with right hand "on tick mark 6".
Also, if I start out at 1:3 and then move the hands down as far as they can go with ratio locked, and then move back up again, the left hand is described as "around tick mark 1" when it visually gets back on 1.
The text was updated successfully, but these errors were encountered: