Lightbox as a Trigger

May 21, 2012

Can you trigger something "close" of the lightbox.. and by close i mean via the little red X that comes with the lightbox view.

I want to .. upon closing the lightbox.. have a layer in the slide under it shown. (if that makes sense.)

thanks in advance.

16 Replies
Angie Johnson

Hi Helene - You could set up your trigger to open the new layer first, then the lightbox slide. The new layer will open under the lightbox, so when the learner closes the lightbox, they'll see the layer. See attached story file. Just make sure that the Show Layer trigger is above your Lightbox trigger so it fires first.

Does that help??

-angie

Heather Emerick

Hi!  As a follow up question, can you use the closing of the lightbox to jump to the next slide?  I have with two response choices.  When the user clicks a response, the lightbox opens to give them feedback.  I'd like to move from the lightbox to the next slide (i.e. not bring them back to the choice slide).  I tried out the great solution above but it jumps to the next slide without ever showing the lightbox.  Thanks!  

Heather Emerick

Thank you for the help.  I also tried converting my slide to a freeform question, choosing the pick one question type and then modifying the feedback boxes.  I like your solution better because I can make it look like the other lightboxes in my project.  It would be cool to be able to manipulate the actual lightbox effect  and use the close button as a trigger, wouldn't it?  Thanks again.  

Ron San

I have a similar situation but a bit complex. I want to set a certain object's state in calling slide, based on what user does in the lightbox. While I am capturing user action in lightbox through a vairable, what I am looking for is a trigger that changes object state AFTER lightbox closes and returns to the calling slide.

I know a workaround is to use "Jump Slides" action instead of Close Lightbox. However I strongly prefer not to start the timeline of the calling slide again after lightbox closes, because it will execute other "timeline state" triggers which I dont want.

is there a solution to this?

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