Trigger next button when using lightboxes

Hi Everyone, 

Hoping someone can jump in with some quick help.  I have a chapter with a main slide that links to eight other scenes that are displayed in lightboxes.  

I need to trigger a change of state on the Next button once all eight chapters are viewed.  

I was hoping to use a "When state of hidden object changes to normal change state of Next button to Normal".  To change the state of hidden object, I was just using a "Change state of hidden object when variable SP changes to be greater than or equal to".  

This variable trigger isn't working, which I am assuming is because I'm using lightboxes and therefore the menu slide isn't tripping an on-entry run of the triggers each time you return to it (?)

I am very short of time on this project, and as such I was hoping someone could suggest I better way to trigger the next button on this slide.  

(FYI - ideally I would require each chapter to be viewed instead of just eight views in total, however, I was trying to safe time on my triggers so just went with one number variable instead of 8 T/F variables). 

Thanks in advance.  Regards Christine

 

4 Replies
Walt Hamilton

Sorry, but this trigger doesn't exist.  "When state of hidden object changes to normal change state of Next button to Normal".  We all wish it did, but there is no "When state changes"

 If this "To change the state of hidden object, I was just using a "Change state of hidden object when variable SP changes to be greater than or equal to"." worked, you could just change the state of Next to normal when variable SP changes, and save a step.

 You're right, you really need 8 T/F variables.  I hope you have a solid reason for using lightboxes, because it makes things a lot more difficult. Because the light boxed slide has a built-in close icon that you can't access, it is possible to return to the menu slide without ever triggering anything that will allow the program to know anything happened.

 Here's a sample story that does what you want, and is simple and reliable: https://community.articulate.com/discussions/articulate-storyline/free-sample-restricted-and-free-random-navigation-using-variables-and-triggers 

Edit - corrected link now works

Take a look at the mixed navigation. It requires you to visit every slide, but in any order before the Next button becomes visible.

Christine Hounsham

Hi Walt,

Thanks for the feedback.  I have taken from this I shouldn't try to cut corners.  (I have done this project quickly as a favour to someone else, in the last weeks before I finish this contract and was simply trying to streamline.  That said I have removed lightboxes and done a bit more on look and feel to show that these scenes are all part of one chapter.  

The link is no longer active but I assume it is probably the same as the method I tried to explain above.  I have now build the triggers out properly using the 8 T/F variables and have attached below in case anyone needs to be able to see how this works.  

FYI - I agree with Walt's point that you don't need to have the hidden object.  I simply do this so that I can copy and paste the hidden object between projects and use it to trigger different actions, as opposed to just putting it on the Next button directly.  

Thanks Christine

Walt Hamilton

Glad you got it going, Christine.

This:

I simply do this so that I can copy and paste the hidden object between projects and use it to trigger different actions, as opposed to just putting it on the Next button directly.

represents best programming practice and can save you a ton of time. Good for you.

There are two things I noticed about your new version

 

This trigger will not set the sp0hh variable, because when the system encounters the jump instruction, it ceases executing triggers and jumps, so the set variable trigger is never executed. I put the trigger to set the variable to True at the end of the target section, so you don't get credit for going through the section until the end.

Also, I name those variables NavVariable1, etc. That way, when I copy the invisible object you mentioned, all the triggers come with it, and the variable names still make sense.