Drag and Drop changing to hidden states

Mar 04, 2013

Hi,

I'm creating a drag and drop template, and I'm running into an unusual problem. My template works like this:

1. three types of objects: arrows with letters on them, pentagon drag objects, and circle target objects 

2. when the mouse is hovered over a numbered pentagon, one of the arrows and pentagon will both light up orange

3. you can drag and drop the pentagons on to any of the circles on the right

90% of the time, I can drag and drop smoothly from pentagon to a circle. But 10% of the time, something wrong happens.

The problem occurs when I try to drag a pentagon onto the circle, and then the arrow suddenly is changed to "Hidden" state and it disappears. The only way to remedy this problem is to change the state of the arrows to normal. So far, I have identified this as a result of adding the hover state.

In this case, I am not allowed to remove the hover states. Is there any way to make sure the arrow doesn't turn to "Hidden" state?

Attached are 3 pictures detailing the situation, and one story file that you can use to replicate the error.

Summary: Sometimes the Hidden state is randomly triggered on an object when there is a Hover state associated with a draggable object.

Any help would be much appreciated!

Thanks,

Binet

8 Replies
Christine Hendrickson

Hi Binel,

Thanks so much for all of the information, images and the .STORY file. Unfortunately, though, I've tried just about every combination I can think of and I'm still not seeing the "Hidden" state issue. 

Is there a specific combination that causes this? Or, does it possibly happen after publishing or uploading, or is it just random?

Thanks!

Binet Lee

Thanks for the reply Christine!

The problem occurs randomly. I myself can't reproduce it on a consistent basis, I basically have to go through trial and error. But even though the error occurs infrequently, it does in fact happen, and when it does, it can cause confusion for anyone trying to evaluate the presentation.

Here is how I reproduced the error:

1. Preview the .story file in Storyline (ease of use, this error can still be reproduced once it has been published)

2. drag a numbered pentagon to the circle across from it

3. do this for all 7 objects

4. hit reset and repeat steps 2-4 until error occurs

The problem in diagnosing this is that it can take somewhere between 30 seconds to 10 minutes to suddenly get a disappearing state, it's essentially random and has nothing to do with (at least I think) how a user drags an object.

Here is another disappearing case I reproduced this morning:


Christine Hendrickson

Hi Binet,

I didn't change any of the options for output (HTML5, etc.), but I did upload to Articulate Online. 

I am currently running Storyline with the latest update, Update 2. Are you running this, as well? You can find this information by clicking on "Help" and "About Articulate Storyline". If you're not running version 2 (1212.1412), you may want to try downloading and installing the update from the link below:

Articulate > Download Storyline Update 2

Here's a screenshot of my publishing options:

Let me know how it goes

Thanks!

Binet Lee

After about 25-30 mins of straight testing, and moving the objects around, I finally ran into the error:

However, I must say that this is the longest it took me to get the error, and that probably under normal circumstances, a student would never encounter this.

The error was replicated much faster when I tested it in Storyline, or when I published it to an LMS, probably around that max 10 minute mark.

Perhaps something about the speed at which the interaction is processed has something to do with this?

Christine Hendrickson

Hi Binet,

Honestly, I'm not quite sure. After that amount of time, maybe a caching issue? Since there's no actual "Hidden" state, maybe it's just breaking after referencing the hover state x amount of times. 

Though, I agree that a user will probably never see this. 

If you'd like, you're more than welcome to send this over to our support staff for testing. Though, I'm not sure they'll be able to reproduce the issue, they may be able to provide some additional information as to why this is happening. 

You'll be able to attach the .STORY file on the second page of the following form:

Articulate Support - Submit a Support Case

Please be sure to include a description of your issue. Please also include the URL for this thread in the form. Also, please share the case number with me. You're welcome to do so here, or in a private message. This way I can follow the progress of the case and update this thread.

Thanks again, Binet

Christine

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