I use Built-In variables (Scene.SlideNumber and Scene.TotalSlides) in the navigation of my courses. When I open a slide in a lightbox the variables are adjusted to the slidenumber of the slide in the lightbox but this also affects the variables on the slide from where I opened the lightbox (Motherslide).
Any ideas how the prevent the variables on the motherslide to update?
Do you want the slide numbers to appear when viewing the lightbox? If not, you could try to hide it while the lightbox is showing, as Len explains in this similar thread. Please let me know if this isn't what you're looking for!
Additionally, if you're comfortable sharing your file, I'd be happy to take a closer look to continue troubleshooting. You can upload it here or share it privately in a support case. We'll delete it from our systems once troubleshooting is complete.
We already moved the field on the motherslide behind the lightbox.
I understand the behavior of the Buitl-In variables and the only 'sustainable' solution would be an extra set of variables for lightboxes or a checkmark to indicate weather the variables should update on lightboxes.
I don't thin a feature request like this would get a serious priority.
5 Replies
Hi Chris,
Thanks for reaching out!
Do you want the slide numbers to appear when viewing the lightbox? If not, you could try to hide it while the lightbox is showing, as Len explains in this similar thread. Please let me know if this isn't what you're looking for!
Additionally, if you're comfortable sharing your file, I'd be happy to take a closer look to continue troubleshooting. You can upload it here or share it privately in a support case. We'll delete it from our systems once troubleshooting is complete.
Hi Kelly,
Thanks for your response.
We already moved the field on the motherslide behind the lightbox.
I understand the behavior of the Buitl-In variables and the only 'sustainable' solution would be an extra set of variables for lightboxes or a checkmark to indicate weather the variables should update on lightboxes.
I don't thin a feature request like this would get a serious priority.
try
result:
https://360.articulate.com/review/content/011fe4a3-1664-4ac7-8f84-f21dc7d4ddf4/review
Jurgen has a good solution
Good solution (workaround) indeed!