Image does not appear after state changed to Disabled.

Oct 27, 2015

Hello,

While developing drag and drop interactions in Storyline 2, I have been experiencing an issue with an image's disabled state that I cannot wrap my head around.

 

How to reproduce the behavior:

I have attached the story file and to observe the behavior, simply drag and drop the correct answer ("Check visual acuity") and submit, or alternatively submit any 2 incorrect options. All the states of the images then switch to "Disabled", where they are re-colored in black 'n white however the correct answer should remain colored and move to the drop target. Unfortunately the image is lost/appears as a solid gray shape.

 

How the interaction works:

The way the interaction works is, the learner gets 2 attempts to drag and drop the correct answer. Each time an incorrect answer is chosen it's state is changed to Disabled. If the user runs out of tries (2) or if they choose the correct answer (Whichever comes first) all 4 images' states are changed to Disabled. The correct answer's Disabled state has the image moved as well as a shape added (To cover up a text box).

 

More about the confusing states:

I have had a lot of issue with this type of interaction. The requirements are very rigid and so we have little  to no wiggle room (I.E: The images must have text labels on-top of them and coloured black as part of the "normal" state but then a white text label on-top of them when they are in their "Disabled" state). We manage to meet this requirement by inserting a textbox as part of that image's state, and style it accordingly. However this is where the problems start... When the "correct" answer's image switches to Disabled, it has to be moved, however the textbox does not seem to move with it. Instead, the text stays at the original location and so I cover it up with a shape. The shape seems to cover-up that issue, but the image is not visible in it's new location.

 

Any insight into what is going on is welcome.

2 Replies
Micheal Walls

Hello Jason, thanks a lot for your time!

I'm sorry I should have explained that originally. The intent was simply to track which of the choices the user had previously selected, so that when the slide reloads that option's state can be changed to disabled.

 

Note:

The triggers in this particular slide are confusing and inefficient, I apologize for using this particular slide as an example. In hind-sight I should have used a cleaner slide hehe.

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