Problem with trigger for 'Visited' state

Hi Sophie

I couldn't replicate the issue. Green tick appears before advancing no matter which button I click. All the triggers seem to be set fine.

Btw. if you insert a predefined button you don't have to add any triggers to change the state of the button to visited - it just happens by itself.

Other option - not showing green tick before advancing, would be to add another true/false variable on every topic slide. If set to true then change the state of the button on the menu to visited.

I'm not sure if it's all clear so I've attached .story file to have a look at. (it's changed for the first topic only).

Hi Sophie,

I ran into similar issues before where SL would not "like" me copying slides, shapes or buttons over.  I definitely troubleshot this in a bunch of different ways and the only work around while keeping your buttons is:

Recreate the target slides (I mean recreate from scratch, don't copy and paste, trust me, I tried)

I've attached my sample so you can see it at work.  Joanna's approach is also a great alternative.

For anyone interested in troubleshooting this, I played around with Sophie's file and figured out that it seems to be related to the Z order of the objects in the timeline on the Menu page. The objects that are lower in the Z order (The "The Daily Commute"  button and the "Your Working Environment" button) show the check mark AFTER navigation to the linked slide happens. For the menu buttons that are higher in the Z order, the check mark shows BEFORE navigation happens. If you move the Daily Commute button up in the Z order a couple of places, then It starts showing the check mark BEFORE navigation, and one of the objects that has now become lower in the Z order shows the check mark AFTER.  The image below (which I think you can click on to see in a larger size?) kinda / sorta explains it.

But that is all I know. WHY it behaves that way, I don't know. And what to do about it? I don't know that either. But maybe this will help someone else dig into it a little further.  

Hi Everyone,

Thanks so much for taking the time to look at the file and try and figure out what the problem is!

I have tried to recreate the button itself and tried to copy and paste from the ones that don't have this problem but nothing seems to work.  I think I will try using the true/false variables as suggested by Joanna and Alexander and will see what happens.

Chris - thanks for looking into this further, that's very strange! Hopefully someone can get to the bottom of that but for now I think I will just have a play around with the true/false variables.

Sophie

I think it is to do with preloading, Chris has highlighted the z-order and I expect the preloader looks at z-order to prioritise what is loaded.

As I understand the preloader it first loads the next 2 slides numerically and then looks at links from that slide. I am not sure this helps solve the issue.

I see it on a few recent projects and it just has to be something I live with or I use variables instead to change a custom state on return.

Hi Phil,

Can you describe what the preloader is please? Is there anything I can do to change the order it uses at all?

Thanks,

Sophie

Storyline preloads content to ensure you don't see the loading wheel very often.  When it first loads it loads the first 3 slides numerically and tries to stay ahead of you.  I don't know of anyway to affect the preloader

Thanks for clarifying, I hadn't heard of that before.

I have managed to fix the problem with the variables now so at least I know what to do if this happens again.

Thanks again everyone for your help.