Forum Discussion
Clicking on one item in a group changes other items to "visited" state
Hello all,
I am attempting to create a scrolling menu (still a work in progress) but there is one issue I am having:
I have all menu buttons grouped together so that clicking on the arrows moves all of the buttons left or right.
This seems to cause an issue with the visited states. The desire is for each button to turn to visited when clicked independently. However, because they are grouped together, it seems that when one button is clicked, all buttons turn to the visited state.
I could probably remove the grouping and create motion paths for each button, but that seems tedious. I was hoping someone has discovered another way?
(pls note: still a work in progress. I am adding triggers to prevent over-scrolling eventually. Wanting to solve this issue first)
See attached SL file
Thanks in advance!
5 Replies
It's the built-in function of the Visited state that is causing the problem. For each step, for both the picture and the oval, edit their states, choose Visited, use the pencil icon to rename "Visited " to something else. SL will automatically change all the triggers that use that state from "Visited" to the new name. In the process, you lose the built-in change to Visited when clicked, but since that is what is causing the problem, you don't care. Since you already have triggers to change the state , you should be good to go. See buttons 4 - 6 in the attached version.
Brilliant! thank you so much!
- You're welcome. PIAWYC (Pass it along when you can).
Coming in a few years late here. I was just bitten by this very unintuitive behavior. Is there a reason why states follow groups? Makes no sense to me. Having the group have its own states would be very powerful, but this way you lose rather than gain capability.
Thanks.
Hey CarlFink1,
I understand the frustration.
Right now, grouping in Storyline is designed to let multiple objects behave as one interactive element. So built-in states such as Hover or Visited are synchronized across that group. That can be useful when a group represents one composite object. However, it also means Storyline can't distinguish between that use case and a group that's only being used to move several independent objects together.
That said, we are exploring ways to give authors more control over this functionality. Are there other limitations you've run into with how Storyline handles grouped objects that have made your builds more complicated than they should be?
