Issue with Slide Layer triggers in HTML5 Output
May 02, 2016
I noticed some unwanted behavior in HTML5 output. It seems that all triggers are loaded for all slide layers at the start of the slide as opposed to when that layer is shown, as in the flash version.
So for instance we are creating software simulations in storyline where the user see's a screenshot of a menu, each layer has a trigger on the up key to move up in the menu, and on the down key to move down. This creates a basic simulation in the flash publish, but in the html5 it fires ALL the layers triggers when one of the keys are pressed, so only two layers become accessible.
I included a basic storyline file to illustrate the issue. In the sample file the numbers 1-5 are shown on seperate slide layers. Pressing up on and slide layer moves to the next number, pressing down moves to the previous. This works fine in flash, but in HTML5 it will break and only show 1 and 4.
We did come up with a workaround, adding a sceneNum variable and adding a condition to each trigger to only fire when that scene is active, but that has issues as well because the keyboard event is still propagating when the timeline start fires for the next slide layer, so changing the sceneNum at timeline start was not an option we had to do it at .25 seconds to stop propagation.
Now our problem is that we have many slides that use this treatment, and we need to add hundreds of conditions to triggers, resulting in hours of additional work that would have been avoided if the publishes simply behaved as expected, and as they did in preview mode.
This discussion is closed. You can start a new discussion or contact Articulate Support.