Initial state and Normal state
Apr 19, 2016
Hi all,
I’ve got a problem that ruins the next interaction in all my Storyline 2 files.
“Next” button has three states: Normal=Yellow, Hover=orang, Disable= gray.
When “Next” button initial state is Normal – everything is ok.
The problem begins when I try to prevent the progress to the next slide by changing the initial state to Disabled (gray) till all interaction ends, then the next button turns to Normal (yellow).
However the next time I’ll open the story file, the Normal state of the button with the Disabled initial state, changes to the color of Disabled (gray) and I can’t reset the Normal state.
I tried that with other states (changing them to initial state) and it always changes the Normal state.
Does anyone knows how to fix that?
11 Replies
example:
Hi Inbal
see if the attached works how you want it to.
I have set the second slide Next button disabled when timeline starts but changes to normal when timeline reaches 3 secs - just to test. Then you can move back and forward between the slides and it is not disabled anymore - I set the slide properties to resume saved state.
Hi Wendy, Thanks for the reply.
The problem is that the Normal state works just fine, but its color changes to the initial state, so it still looks disabled even though it’s Normal
Hi Inbal!
Sounds like you are running into an issue that we have reported to our QA Team.
I updated the file that Wendy shared above, but I suspect you are going to see the same issue again.
Seems related to the Disabled state, so I've attached another story utilizing the hidden state and perhaps this will work better for you.
I will add this thread for our QA Team for both user awareness and so that I can update when applicable.
Hi Leslie
what is the issue? Is it only with custom Nav buttons?
With any button it seems when utilizing a disabled state - the formatting is lost - we haven't put our finger on it yet I don't think.
Is it only buttons, or does it affect shapes, too?
The report we have thus far is buttons. I'm not sure I've seen anything about shapes. Do you have an issue Walt?
No, just checking. Thanks.
My personal philosophy (which involves a lot of opinion) is that seeing a clickable object that doesn't work serves only to frustrate a user. Pedagogically, clear instructions are a much better option.
Meaning you'd prefer a hidden object vs disabled anyway?
That is absolutely my personal preference.
If it doesn't function, don't distract the user with the clutter.
This discussion is closed. You can start a new discussion or contact Articulate Support.