Forum Discussion
Clicking on one item in a group changes other items to "visited" state
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?