Sorry, I probably should have been more specific in my original post!
As soon as I add the visited states, and I click on the buttons in my menu, the lightbox closes, but does not go to the slide that it should. (FYI each button has a "close lightbox" and a "jump to" trigger on it).
I attached the .story file to this post, if you could take a look at it and let me know if there is a solution that would be great!
I took a look at your file, and saw the behavior you're describing in regards to the menu items which had a state assigned to them not working as expected in terms of closing the lightbox and jumping to the particular slide. I saw a similar issue reported to our QA team where it was causing issues when using the "down" state. So as I was doing some additional testing, I created a new state called "Test" that was changed for the Chapter 1 box when the user clicks on it, then closing the light box and jumps to the appropriate slide. This one seems to work as expected. I also modified the revisiting behavior for your menu slide from "Reset to initial state" to "resume saved state" so that the state change to "Test" would be kept when I revisit it. I'll share this with our QA team as well, but in the meantime I'd suggest using the workaround mentioned of creating a custom state.
Just as a reminder, the attached file shows:
- in introduction box with no states, works as expected
- the Chapter1 box has a custom state of test (works like your visited state) and works as expected to close the lightbox and jump to slide
- the Chapter2 box has your visited state, and the jump to slide trigger does not work as expected regardless of trigger order.
However, I'm assuming that means that I will have to create triggers for each button so that they change to the "test" state, instead of having a visited state that is "automatic".
7 Replies
What exactly happens when you add Visited states? Maybe you can post your file (or a portion of it) here so that we can have a closer look.
Sorry, I probably should have been more specific in my original post!
As soon as I add the visited states, and I click on the buttons in my menu, the lightbox closes, but does not go to the slide that it should. (FYI each button has a "close lightbox" and a "jump to" trigger on it).
I attached the .story file to this post, if you could take a look at it and let me know if there is a solution that would be great!
Thanks,
Allison
Switch the order of the triggers so that the "JumpTo' trigger comes BEFORE the 'Close Lightbox' trigger.
Hello,
I tried switching the order around as well, but what happens is that the lightbox never closes (see image below).
Is there any way to make it close the lightbox and go to the slide?
Thanks,
Allison
Hi Allison,
I took a look at your file, and saw the behavior you're describing in regards to the menu items which had a state assigned to them not working as expected in terms of closing the lightbox and jumping to the particular slide. I saw a similar issue reported to our QA team where it was causing issues when using the "down" state. So as I was doing some additional testing, I created a new state called "Test" that was changed for the Chapter 1 box when the user clicks on it, then closing the light box and jumps to the appropriate slide. This one seems to work as expected. I also modified the revisiting behavior for your menu slide from "Reset to initial state" to "resume saved state" so that the state change to "Test" would be kept when I revisit it. I'll share this with our QA team as well, but in the meantime I'd suggest using the workaround mentioned of creating a custom state.
Just as a reminder, the attached file shows:
- in introduction box with no states, works as expected
- the Chapter1 box has a custom state of test (works like your visited state) and works as expected to close the lightbox and jump to slide
- the Chapter2 box has your visited state, and the jump to slide trigger does not work as expected regardless of trigger order.
Great, thanks! I'll have to test that out.
However, I'm assuming that means that I will have to create triggers for each button so that they change to the "test" state, instead of having a visited state that is "automatic".
Thanks for your help in any case!
Allison
Hi Allison,
Yes, you'd need to set up the triggers and state for each button. If I hear any further from our QA team I'll also be sure to let you know!
This discussion is closed. You can start a new discussion or contact Articulate Support.