Forum Discussion
Set initial state on all slides at once for an object.
I'm building a template with all the slides (200+ slide options) to include a character object set up with custom states. The other states are the other 4 character options.
Note: Poses may change based on the slide layout, but they would all have the same state names.
I have triggers and a variable set that will choose the chosen facilitator when the timeline starts on each slide. Still, I want the designer to see their choice on the slide as they are building without having to go to preview or publish to see the character change.
This is not about how the learner will see the lesson. It is for the Instructional Designer to see who they want as their choice in slide or story view.
I know the designer can set the initial state to the character of their choice and then it in all views: Slide view, Story view, Preview mode and Published. But to do this on all slides (at least 50) every time they use this template is time-consuming and defeats the purpose of this template for rapid designing.
I want to be able to set ONE trigger or variable or code that will execute setting the initial state to one of these custom name states on all slides in the project in one "click."
Attached are the storyline file and a pdf that shows the visuals beside what I am trying to explain above.
Thanks for your help.
Just throwing this out there: Would creating copies of the original project - with each copy having a different character set as the guide - do the trick?
Or..or...you could tie state change triggers to keystrokes tied to each character. In the attached file, I have it set up so the character changes to "Thomas" when "1" is pressed; "Jet" when "2" is pressed, and so forth.
Thanks for the feedback and the other option, but this still just changes the states when previewing and publishing views. I wanted it to change on the slide (base layer) when designing.
The keystroke triggers work for quickly changing the slide without having to reset the variable for the who thing. I will definitely incorporate this in the template for my team.
Regarding separate templates for each would be a maintenance nightmare - keeping it all in one works best for our team.
Thank you again, Daniel. I appreciate you taking the time.
