Forum Discussion
Dial operation incorrect
Hello knowledgeable community.
I am attempting to use a dial to change the state of 5 buttons from normal to visited when the dial points at the button. While I thought this would be easy and look really good, i am finding it very hard to do.
When I move the dial towards the first object, it changes it's state, bingo. However, when I copy the trigger for the second button (and change it to button 2), it changes the state of button one and two when I point the dial at button one.
I am sure that whatever will solve this is really simple, but I just can't see it. Ignore the look of the slide, it is in progress.
Any ideas?
- JudyNolletSuper Hero
The trigger in the image shows state changes "When Dial 1 turns." That means the trigger will run every time the dial is turned, no matter where it's pointing.
To control an object based on the position of the dial, add a condition that checks for a given value of the variable. For example, that might look like this:
- SteveLydonCommunity Member
Thanks, I had a little look at that. I will try. Many thanks for taking the time to reply.
- MichaelHinzeCommunity Member
Have a look at the attached and see if that's what you wanted. I changed the condition you used in the change state triggers to reference the dial variable.
- SteveLydonCommunity Member
Again, brilliant. Thanks. That makes sense now. I forgot to add a position variable. All working now. Many thanks.
- SteveLydonCommunity Member
- MichaelHinzeCommunity Member
Based on the screenshots, all looks good. Can you share the file (or that one slide) here, so that someone can have a closer look.
- SteveLydonCommunity Member
Michael,
Thanks for your help. I assume I use Review to share it?
https://360.articulate.com/review/content/527534a2-f7d2-460e-be2d-45e93bfcb0ef/review
- MichaelHinzeCommunity Member
I meant the .story file.
- SteveLydonCommunity Member
- MichaelHinzeCommunity Member
I think the issue was that you used the built-in Visited state to display the text AND that same text is already there in the Normal state. Built-in states like Normal and Visited are displayed in an additive way, and with both states having the same content, it looked like the additional text did not show up but in fact is displayed below the Normal state content. To avoid that, I created a custom state Completed for each element that that works as expected.
- SteveLydonCommunity Member
Brilliant, as always, Michael. Many thanks.