Use cases, part of a course about tracking the state number of interactive and non-interactive objects, and using that number in Submit and Check actions.
Intro
The introduction of Multistate objects have changed my workflows a lot.
It is a pity that we don’t have a system variable which allows to easily identify the state of a multistate object, either by its number or by its name. For that reason I want to share an example project showing several use cases where tracking the state number is achieved and used to check out success. This project will be used in tutorials, but you’ll be able to check out the result in this project:
Three of the use cases have multistate objects which are also buttons: the two Physics cases and the Slot machine. The Carousel example (with Forced view) has a non-interactive multistate object. Number of states vary from 3 to 10 states. I start state numbering with 1 (for the Normal state). You’ll see that number appearing in the Carousel but it is used in all cases. For the design I used some slides from the Quick Start Project ‘Diverse’.
You must be logged in to post a comment.
