While working on custom players for courses using only controls on a master slide for slide navigation, I am finding serious system instability creating a progress bar with 100 states (one for each percentage). When publishing a proof of concept with only three slides with minimal assets (think one picture on each slide), Chrome and IE11 are either taking extraordinarily long to load or hanging, depending on the workstation I'm using.
Has anyone else had a similar experience when using so many states? And, if so, what was your workaround?
i want to confirm that you are working and publishing locally with the file as described here. Also, when you are testing the content, are you using its intended environment and not testing locally?
I'm testing everything locally, including working, publishing, and viewing. If it helps, even my previews were starting to hang with so many states and triggers on one slide.
I want to make sure I am understanding you correctly. You're suggesting that if previewing a project using the Articulate player is causing it to hang, I should move directly to publishing to a web server?
Okay. I've gone ahead and done that. It's still hanging, though.
I ended up splitting the master slide with the object with 100 states and 100+ triggers into five master slides with 20 states and 30+ triggers. The slides are behaving much better now.
I'm curious if anyone has run into similar issues and have done similar workarounds.
RE Emily: I've read the stories and downloaded some demos of people accomplishing amazing things with countless states and triggers. I was curious to see if anyone else had experienced issues when using so many or had tips for using maximum states with 100+ triggers per slide.
7 Replies
Hello Chris!
i want to confirm that you are working and publishing locally with the file as described here. Also, when you are testing the content, are you using its intended environment and not testing locally?
Hi Emily,
I'm testing everything locally, including working, publishing, and viewing. If it helps, even my previews were starting to hang with so many states and triggers on one slide.
Hi Chris!
Testing locally cause have security issues and cause various features to fail. You might want to view the link I shared above for testing options.
I have heard other members before share that they have used a good number of triggers/states on slides with no issues.
You may want to follow the steps here as well.
I want to make sure I am understanding you correctly. You're suggesting that if previewing a project using the Articulate player is causing it to hang, I should move directly to publishing to a web server?
Hi Chris,
You will want to test the published output from the intended web server to see how it should behave.
Okay. I've gone ahead and done that. It's still hanging, though.
I ended up splitting the master slide with the object with 100 states and 100+ triggers into five master slides with 20 states and 30+ triggers. The slides are behaving much better now.
I'm curious if anyone has run into similar issues and have done similar workarounds.
RE Emily: I've read the stories and downloaded some demos of people accomplishing amazing things with countless states and triggers. I was curious to see if anyone else had experienced issues when using so many or had tips for using maximum states with 100+ triggers per slide.
Thanks for the update Chris,
i am sure if other members have had this issue they will jump in with some ideas.
This discussion is closed. You can start a new discussion or contact Articulate Support.