Dial not incrementing correctly
Jun 22, 2020
By
Nisha Makan
Hi I have a dial in SL360, ranging from 1500 - 4500. It has an initial start point of 2000 and step value of 500. When previewing the dial, the pointer leaves 2000 and when moving forwards it works fine. When moving backwards the pointer doesn't stop at 2000 again when dragging, it skips it and moves from 1500 - 2500. Not sure why it misses that number. I tried deleting the dial and creating a new one and the same thing happened. It's my first time using dials so not sure what I'm doing wrong?
10 Replies
Hi Nisha, are you able to share your Story file?
Hi Sam - unfortunately not due to confidentiality
Possible to remove the confidential bits and just provide the dial?
Good idea, have uploaded
Hi Nisha, I was not able to replicate the problem. I tested in Edge, FF and Chrome. Which browser are you have trouble with?
https://360.articulate.com/review/content/46818350-4dc4-484e-b481-e6675d7cace9/review
Oh hang on, it appears to be the later release of Storyline. I remembered I'd rolled back to January this morning, and it works in the January release, but just updated to May 19, and it's broken. Skipping the 2000 as you say. Interestingly when using the keyboard to navigate the dial, it appears to go to 2000 (not visually) but takes the extra key press to pass it.
Hey Sam - your version worked fine for me too.
This was just previewing in Storyline. Just did a quick test publishing to review and was able to replicate error in Chrome but it worked fine in IE
https://360.articulate.com/review/content/4e969edf-3a08-40d7-9af3-0aba8c31857e/review
OK, that's good to know, am guessing it's a bug with the May version then
Hi Nisha, as a work around just have the dial start on 3,000 initial, then on timeline start set the Dial2 variable to 2,000. This worked for me and corrected the issue. I first tried having the initial value on 1,500 but then it wouldn't go back to 1,500.
I'd recommend you open a case for this one.
Awesome, thanks so much Sam, your workaround worked for me :)
Yes, will put a case through for this
This discussion is closed. You can start a new discussion or contact Articulate Support.