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
Tom Kuhlmann

What you can do is reverse the triggers.

  • Set the buttons to initial state normal.
  • Trigger to change to disabled if variable = false
  • Then need a trigger to change to normal when condition of variable is met.
  • Also need a trigger to change the state to Visited when the condition of previous variables are met. Here's how I set it up and it works.
Joseph Dowling

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.

Joseph Dowling

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

This discussion is closed. You can start a new discussion or contact Articulate Support.