Forum Discussion

IFISGroupe's avatar
IFISGroupe
Community Member
3 years ago

Recent Storyline update issue on recognizing the 'not Normal' state of objects

Hi,

I'm encountering an issue regarding a workaround for drop down answers in a fill the gaps text that was created a couple of years ago. A fairly recent update (2 to 3 months ago top) came to disrupt the format.

The logic here that used to work was that two objects out of the frame represented the correct or incorrect state for the answer. Triangle 'True' becomes selected once the rectangles are in a 'not Normal' state, with conditions of the actual correct answers being the state of the rectangles.

So the problem here is that up-to-date Storyline 360 doesn't actually recognize the Not normal state which prevents the logic that allowed Triangle 'True' from ever being in a selected state that would validate the exercise.

See file attached for the specific example.

(Valid answers are shown in the "Bonne réponse" layer)

Thanks in advance for your help !

storyline 360
  • MariaCS's avatar
    MariaCS
    Staff
    3 years ago

    Hi, IFIS.

    Thank you for sharing your .story file!

    We have a possible bug logged where the trigger to change the state of "Object2" when the state of "Object1" (or a combination of objects in a condition) changes is not working when using "Is Not Normal" condition.

    I want to share some information on how we tackle bugs,  and we’ll let you know as soon as we have an update on this issue.

    As a workaround, can you separate your trigger so it specifies the state the rectangle has to be in (for example, "when the state of rectangle7 is reponse2")?

  • WaltHamilton's avatar
    WaltHamilton
    Super Hero
    3 years ago

    IFIS,

    Since the beginning of time, the built-in states (hover, selected, etc.) all report themselves as Normal states, so "is not normal" only works with custom states. As Maria says, use "is [name of state]", instead.

Related Content