It shouldn't as you'll see from Phil's example, but if you're experiencing any performance lags while editing or in your published content you'll want to confirm that your computer matches with the system requirements outlined here.
Answer to the Ron question, I think the number of triggers is free, but if we talk about number of variables, I'm not sure. Each of variables is sent to LMS and as we know, suspend_data has only 4096 characters. You should call the JS function GetDataChunk and check the length of suspend_data.
8 Replies
I built a course withover 8,000 triggers on one slide, there is no real limit
thanks phil!
thats great to know.
i also assume there wont be disproportionate performance degradation over the web purely due to high number of triggers.
You can see the course I built on the showcase
View Now
Seems to work fine
Hi Ron! Looks like Phil has you taken care of here
yes thanks to phil for the answer.
can you please confirm that such high number of triggers will not result in performance degradation?
Hi Ron,
It shouldn't as you'll see from Phil's example, but if you're experiencing any performance lags while editing or in your published content you'll want to confirm that your computer matches with the system requirements outlined here.
Answer to the Ron question, I think the number of triggers is free, but if we talk about number of variables, I'm not sure. Each of variables is sent to LMS and as we know, suspend_data has only 4096 characters. You should call the JS function GetDataChunk and check the length of suspend_data.
thanks kamil.
an update from my side. i more than meet the system requirements for the software.
i have 200 questions in my question database.
it takes:
- 2.5 minutes to save the file.
- 9 minutes to publish
- thankfully there was no noticeable lag in the output
so there seems to be an undesirable performance in the development environment.
unfortunately i can break it into multiple storylikne files because i need the clock functionality.
not sure if there are any workarounds to reduce the publish ans save time.
This discussion is closed. You can start a new discussion or contact Articulate Support.