Interaction based on linked Conditions without scripting.
that’s what’s possible:
linking conditions by “and” -> every condition must be met
linking conditions by “or” -> any condition can be met
When the count of triggered (running custombehaviors as hype-behavior) conditions is equal to the count of linked conditions the result will be examined and a predefined hype-custombehavior will be triggered.
A scene or file can have several hypeConditionLinker-instances
To setup an instance you’ve got to add some data-attributes to an hypeelement:
data-logic-namespace -> the unique name for the instance data-logic-if -> a string that lists some custombehaviornames that are linked eather by "_and_" or "_or_" data-logic-then -> a string that represents a custombehaviorname to be triggered* data-logic-else -> a string that represents a custombehaviorname to be triggered optional data-documentwide -> a string: true. if set the instance will persist on scene changes *when linking the instance with "_or_" data-logic-then is obsolete. instead a custom behavior will be called that includes the solved conditions as a name (-> condtionOne_conditionTwo_conditionX)
Feed an instance:
to feed an instance with a condition set up an empty custom behavior whose name includes the namespace of the instance and the current condition divided by a pipe ->
namespace | condition
trigger this custom behavior from any in hype possible behavior … (timelinebavior, click, scene load …)
i guess this seemed more complicated than it is …
the attached file will show a setup that combines two multiple choice questions to one unit. the result will be displayed in the last scene.
hope it’ll work!
HypeConditionsLinker.hype.zip (68.3 KB)