Player Buttons and Layers in IE
Nov 01, 2019
Hello!
I'm posting in the hope someone can help me with an issue that's driving me crazy.
We have since introduced the use of the built in player buttons and have gotten rid of our custom made ones. I love that triggers/state changes can now be added to the player buttons.
The problem I am facing is this:
I have a slide with about 7 layers, to trigger in a layer I use a variable 'Layer_Count' that adjusts to a value at the start of each layer timeline (e.g. Layer 1: Layer_Count = 1, Layer 2: Layer_Count = 2 etc...) and I then use a trigger such as 'Show layer 2 when user clicks Next button IF layer_Count =2'.
I can't recall having any issues with this before up until this week. In Chrome it works absolutely fine still, but when previewing in IE, it seems to be jumping to the very last layer. It seems to handle 1/2 called layers, but when I have about 6/7 that's when it is struggling.
I have attached the storyline file and a Review link so that you can preview in IE and in Chrome.
Any advice on this would be fabulous, I don't want to not use layers as I don't want to have a course will 100s of slides.
Thanks
https://360.articulate.com/review/content/e88ec531-f7d1-42ec-adff-4e868090bd6e/review
3 Replies
Hello, it looks like in your Player Triggers on the main timeline you have both Layer_Count 3 and 4 both going to the same layer so it is going to stop there, then it also looks like you need to add the rest of the triggers i.e. 6/7 etc. to go to the rest of the pages.
One other observation/suggestion, you could set the Next to Normal at end of timeline vs. setting a timeline reaches value, and shorten your timelines for each layer to the same timing.
Hi Jeff,
Thanks for your comment. I've been in converse with Articulate and it seems the underlying problem is when publishing the course in Flash, the player button doesn't work as it is instructed to do.
Can't yet publish in HTML5 either due to missing fonts - our IT Techs are on it though!
Thanks again
Caroline
It seems I am still encountering this issue, even in Chrome. I have a case open with Articulate but if anybody else has any thoughts around why this may be happening then please let me know.
This discussion is closed. You can start a new discussion or contact Articulate Support.