Forum Discussion
Objects set to "Visited" initial state do not respond to clicks.
I have a series of slides that represent the stages of a flowchart. Each slide has an orange "information" button that users click to display a new info layer, then they move to the next slide. The button has a Normal (orange) and Visited (grey) state.
When the user advances to the next slide, the info button from the previous slide is set to "Visited" (grey) for Initial State, but I still want the user to have access to that layer of information. However, the button set to "Visited" is not active and doesn't respond to clicks.
The new button for the slide works and when clicked, turns to "Visited" (grey). You can also click it again in the visited state to view the info.
So why does the button set to "Visited" as initial state not work?
Example project attached. I am on the most recent version of Storyline.
You should add "Disabled" state for this to work.
9 Replies
An object in the Visited state should still run its "when clicked" triggers. Here are a few things I tried:
- I changed the button's Initial state to Normal. It is clickable.
- In addition to that, I added a T/F variable that is changed to True when the user clicks the ?1 button on the first slide. On the second slide, I added a trigger that changed the ?1 button to Visited when the timeline starts with the condition that the variable = True. Thus, the button is Visited right away. And it works.
Unfortunately, I still have no idea why simply having Visited be the Initial state somehow disables the button.
In other words, that is what's politely called "unexpected behavior."
I suggest you submit a case directly to the Articulate staff. You can do that here: https://access.articulate.com/support/contact
Include a copy of the file. I also suggest that you give them a link to the post, so they can see the testing I did.
Thanks for the reply and testing, Judy. I will definitely file a bug (not polite :) ) and see what they say. In the meantime, I can use your workaround.
You should add "Disabled" state for this to work.
Thanks Nedim. I can't believe that actually works. It's so unintuitive. Do you have any idea what's happening behind the scenes to make it work?
This goes beyond what might seem logical at first, we have to think in terms of how Storyline works. When only the "Normal" and "Visited" states exist, setting the initial state to "Visited" causes Storyline to treat the button as if it has already been clicked, and doesn't respond to clicks again (because the built-in logic says, "you’ve already done this"). Storyline assumes it shouldn’t behave like a fresh (clickable) button anymore. The "Visited" state isn’t just visual, it also signals to Storyline that the button has already been activated. As a result, any trigger attached to it may not fire.
Now, the reverse logic:
When you add a "Disabled" state (even if you never actually use it), Storyline starts treating the button differently. It’s almost as if it thinks, "Hmm, this button could potentially become disabled, so I better check whether it actually is." As a result, Storyline re-evaluates whether the button should still respond to clicks.
Of course, this is just my interpretation. It’s not something officially documented or confirmed by Articulate. Just an attempt to explain what seems to be happening.
JudyNollet Lol...I’ve already got a few hats lined up...I just rotate them between bugs like thisNedim : Here's my interpretation. Storyline doesn't usually prevent a user from someone from clicking an object more than once. I've clicked Visited buttons many, many times. So I'd still call this situation "unexpected behavior."
In any case, I need my hat. Otherwise, folks wouldn't recognize me. However, I sure could use some bug spray!
A trigger set to run when an object is clicked should run whether the objec's state is Normal, Selected, Visited, or custom.
As amorrissen said, it makes no sense that adding a Disabled state to the button makes the button's Visited state work when Visited is the Initial State.
That's so weird it almost makes me want to hang up my hat... 😏
