Trouble with True/False Variable and changing state of button to "visited" with check mark

Mar 13, 2015

Hi. I followed the tutorial on how to use a true/false variable to create a "visited" state for the buttons on my menu page, but it's not working.

When I created the trigger to change the variable to "true", I put that trigger on the last slide of each line that the button takes me to. Some buttons already change to the "visited" state as soon as I click the button (before the next slide even shows up).

On top of that, the button is at the "visited" state when I click the "previous" button on the 1st slide, even though the variable is not supposed to change until I click the "next" button on the last slide of the sequence.

 

I was able to successfully create another ELM using this technique, but it isn't working for this particular ELM. And the strange thing is that it works for some buttons but not for others. (And it's not always the same buttons!)

If someone could help me resolve this issue, I would greatly appreciate it.

I've attached the file. The page with the buttons is the second slide.

Thank you!

19 Replies
Michael Hinze

1. Set the slide properties on slide 1.2 to 'Reset to initial state'

2. I suggest to create a custom state, e.g. MyCompleted for each of the menu buttons and show that state based on the T/F variables. The Visited state is a built-in state which is automatically displayed when an object is clicked. So, in your case using this built-in state may not be the best way to show completion of a section.

cindy lucas

Here's the file I'm working on. https://www.dropbox.com/s/chw4gr9nydlhsn6/Budgeting.story?dl=0

Leslie these are two separate issues.

1. The buttons on the menu were changing states before the user gets to the triggers. I created a new stated call viewed and created five variables. One for each button. Once they turn true the button should change it's state. Now none of the buttons will change states.

2. Sixth button on the menu should change to normal based on a variable. It doesn't.

I've been having issues with variable and triggers working as intended all week. I've spent most of the day just trying to get it work like it's supposed to. Any help is appreciated.

Phil Mayor

Hi Cindy

See the attached file, using a numeric variable here will not work unless you add some conditions, as what would happen if the revisited the same section 4 times.  

I have switched it to a true/false variable for each section which is changed on the return to menu button, not how the trigger is before the jump to trigger (as trigger order is very important and any trigger after a jump to is ignored, this is why your trigger was not working)

I would also look at your return to buttons and make them consistent two say menu and the other two do not.

This should work fine, I could not test as preview kept throwing an error.

 

Phil Mayor

I have done the state change for the final button, just replicate that using timeline start trigger that I added to change the final button but instead of four conditions just use the specific one you need.

I noticed you were using when variable changes, but the variable only changes on that slide at that point when you return that will not work unless you set it to resume saved state, hope this makes sense

 

Michael Hinze

See attached file. 

1. I changed the trigger order so that your menu1 variable is increased BEFORE jumping to a new slide.

2. The trigger condition "when variable Process changes" only applies to the slide where the change actually happens (which is NOT the menu slide). I changed that trigger to When timeline starts if the variable is true.

3. 'Visited' is a built-n state that is displayed automatically when an object is clicked. I changed the Budgeting Process button to have a Completed (custom) state, instead of the built-in Visited state.

Phil Mayor

I cannot preview or publish your files to throws errors, but would be confident it would work, I have switched off now so will
Look again in the morning, hopefully Michael can help. Look at the principles that Michael and I pointed out it should be simple to troubleshoot with those, Phil

Sent from my iPhone

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