I don't understand the point of variables if they won't work.

Hi Dan

I take it back (I think). After a bit more investigation, I have managed to create a version that doesn't work - when I think it should work! i.e. there may be a bug...

In the first version of my test Story above, I changed the state of a Button based on a trigger linked to the start of the timeline on the base slide. If all four checkmarks were true when the slide started i.e. all four objects had been clicked - the button changed... This worked fine.

So, I tried doing what you had suggested and made the trigger to change the state of the button linked to a change in the variable CheckMark4. So I could see what was going on, I added a layer that delayed the jump to the next slide by 5 seconds when the final (fourth) object was clicked and CheckMark 4 was changed - sure enough the state of the button changed when the last object was clicked...

BUT, when I return to this slide, the button has returned to its initial state.

Hmmm?. My understanding was that, if I change the state of a button in a slide, navigate away from that slide and then return, that button shoud be in its changed state NOT back to its initial state. So I think there may be a problem - not with the way variables work - but with the way 'states' work....

Phil, I trust your judgement on this. Has the attached Story hit a bug? Or have I just got my logic wrong??

 NOTE there is a 5 second delay before you jump to the next slide after you click the 4th object