Reserved State Names

Apr 02, 2014

Hi, this is a bit random but probably known and documented but I couldn't find it.

If I create a graphic with the state "Checked" and set a trigger to activate that state - everything works fine. When I close the Storyline file and open it up again - it no longer works, the Checked State has been renamed "Selected" and the Trigger code shows Invalid State. This is wholly repeatable. Simple example before and after below.

If Checked is a "Reserved" state is there a list of other reserved states someplace? (And the handling could be a bit more helpful!) Thought I was going mad for a moment...

 

We're still using Storyline Update2: 1212.1412

Using an alternate state name fixes the issue.

Thanks

John

12 Replies
Greg Faust
Ashley Terwilliger

Hi John and welcome to Heroes! 

"Checked" is not a built in state, but they're all defined here. 

You mentioned you're still on update 2 of Storyline? Are you able to update to update 5, as that's the most recent update with a number of bug fixes. 

I encountered this thread while researching this oddity. Here's the bottom line: Do NOT use "Checked" as a state name. It might not be built-in or explicitly reserved, but it's definitely taboo. Storyline will change the state name from "Checked" to "Selected" when you save/load or copypaste the offending object. This will screw up triggers and make the object behave as though "selected" is one of its states.

As for a list of reserved states, I have yet to find one. This issue is beyond the scope of the Support article Ashley linked.

Greg Faust

Though I discovered this gremlin independently, I wasn't the first. It's been a few years, Leslie, but you actually did see it, in this thread

The issue is easy enough to avoid (don't call a state "Checked"), but if your team wants to look into it, I'll be happy to help.

A saved test file doesn't show anything interesting. If you would like to duplicate this bug:

  1. Make a new Storyline presentation
  2. Insert an object (e.g. a square)
  3. On that square, add a state called "Checked". Click "DONE EDITING STATES".
  4. Copypaste your object.
  5. Check the new object's states. Whereas the old object has states "Normal" and "Checked", the new object has states "Normal" and "Selected".
  6. Save, close, and reopen the file. Now BOTH objects have states "Normal" and "Selected", while the "Checked" state is nonexistent.

My testing used Storyline 2, update 10.

Leslie McKerchie

Hi Erin - well, the discussion has led to some further discovery and we have shared this information with our QA Team to investigate further as we are finding some unintended behavior as you can see above. I do not have an update or list to share with you at this time, but this thread has been included for user awareness and for update when applicable.

This discussion is closed. You can start a new discussion or contact Articulate Support.