Need Help with Triggers
I am creating triggers based on my customers' requirements. Initially, the "next" button should be disabled. Once the requirements below are met, the "next" button should be enabled. Users should ...
Forum Discussion
Thank you for sharing the training. That really helps.
I have run into a scenario not covered by the slides on the training, and I'm wondering if you have ideas. I am using the objectives slide, shown below. I want the user to click on each objective and then spend a certain amount of time reading each objective before it being considered "complete". I am thinking this may not be possible on this particular slide as there is no "close" button for the objective that would be activated by the timeline for that layer reaching a certain point. Is my understanding correct or is there another way you can think of doing it?
The only other way I could think of doing this is by having the timeline on the base layer be long enough for the user to read the instructions and each objective. Once the required amount of time has passed, then the next button would activate. While it wouldn't force the user to spend time on each objective, the overall time required on the slide would be similar.
As a fast reader myself, I really dislike the timing requirement. However, my client is a large enterprise company, and they have certain requirements for their trainings, including minimum timing.
As we all agree, it's frustrating for the users to have to wait beyond the time it takes them to read the content. However, I also understand client demands...
To meet that demand, I think the best approach in the above case is to force the user to click the buttons in order. Start by showing only the first button. When that is clicked and its content is revealed, wait a given amount of time to reveal the next button.
Here's an easy "timer" to use:
- Put an object off the slide.
- Give it a motion path that lasts the desired amount of time for the delay. (Be sure to delete the trigger that runs the motion path when the timeline starts.)
- In addition to the button trigger that shows the content, add a trigger that moves the off-slide object on its motion path when the button is clicked.
- Then use a trigger that changes the next button to Normal when the motion path completes. Note: You could track which button to reveal via variables. But it might be simpler to just use a separate "timer" object for each button that has to be revealed.
That still forces the user to spend a given amount of time on the slide. But at least it spaces it out, because they can't read all the content right away.
