Custom menu using variables to enable buttons - but visited state not triggering
Jun 15, 2018
Hi all,
I going in circles on this one, please help.
I have a course with 6 areas with each needing to be visited, to this end I have created a change to true variable at the "start of the timeline" on the last slide of each area.
With initial state set to disabled and to normal when variable becomes true, I have managed this but...this is stopping the visited state of the buttons from working.
I have tried initial state as normal and to change state to disable if variable is false which is the start value, but this causes it to lock on the disable no matter what the value, not sure why.
I've reinstalled Storyline 360 incase it was an update that caused the problem, but no luck.
Please help, I have attached a test version of what I'm trying to do.
Joe
9 Replies
The visited states are activated when you click on the button. You can see that happen very quickly before it jumps to the next slide. You have a trigger set to change the state to normal, thus you are getting rid of the visited state.
The only one without a trigger is the first button and that's why it remains visited.
What you can do is reverse the triggers.
Thanks heaps Tom,
I was hoping that under your second bullet point if variable = true the button would become normal and visited would behave as normal.
What you have suggested will provide the function needed, cheers Tom.
Joe
Sorry Tom spoke too soon,
I have added triggers to control each state depending on the variable, but the 2nd area will not become normal even though there's a trigger telling it to.
Why does it lock itself to disabled?
I've tried different ways of the trigger seeing the variable i.e. not equal too and number variable
Thank you, I'm sure I'm missing something. I've attached this version.
Joe.
It seems to be working for me. I assumed that you want the buttons disabled and then progressively enabled to normal as the modules are completed.
https://360.articulate.com/review/content/da6a3b43-12a5-486d-a490-fd7625020c96/review
Am I missing something?
I'm doing the same but with different results.
I'm thinking there may have been some issue with the latest update, I saw something in a recent thread regarding button state issues since an update.
I have Articulate 360 ver: 3.16.15842.0 and using a pc with Windows 10 OS.
I've attached its behaviour
Thanks again for your help on this.
Joe
Do an update of SL and see if it works. The current version is 3.17.... I see in your video that it says to update 360.
That was it, triggers are now working.
Thank you very much for your help.
Glad you got it working.
This discussion is closed. You can start a new discussion or contact Articulate Support.