Something wrong with Disabled state?

I'm building a course that has six parts that learner will complete one by one. On the menu page (slide 3) I have set the initial state of parts 2-6 to be Disabled (they will change to state Normal after contidions are met, check the triggers). However, there seems to be something wrong with the Disabled state. In preview mode, the colours of the parts are like they should (grey circle and grey font) but when I click them, they do the trigger that should be done only when the state has turned from disabled to normal. So, they look like they are disabled, but they aren't.

The parts are groups consisting of two elements: circle and rectangle with text. I've set the right states and initial states for each elements as it's not possible to set states for a group.

I have built this kind of functions many times and I haven't had this kind of problem before. Help me, please? 

6 Replies
Rita Korjonen

Hi Michael and thanks for reply! Unfortunately this solved only part of my problem and created another one. Now I have Jump-to-Slide triggers only in ovals, not in the groups. This is what happened:

  • Disabled state seems to work only partially: Clicking an oval with disabled state doesn't jump to slide (correct) but the state of the oval changes to Hover when mouse hovers over it (not correct). Previously when I've used the disabled state, it has blocked the hover state, too. 
  • I want to build this in a way that learner can click either oval or rectangle to jump to slide. By adding Jump-to-Slide trigger only in ovals, learner has to click the oval as rectangle doesn't have that trigger. Well, I could add the triggers to rectangles too, but in that case the hover functionality doesn't work how I want. This is why I have groupped them :)

I guess that there is some kind of a pug in Storyline. I'm 99,99% sure that this has worked before. And due to my logic, Disabled state should make any element literally disabled - it doesn't react to anything.

Lauren Connelly

Hi Rita! 

Thank you so much for sharing your project! It's always so helpful to see what you're looking at.

It looks like the triggers are what is causing the issues. I was able to open your file and see the user can access any slide without completing a previous slide.

I was able to change that, by changing the conditions. 

Here are the steps I took, let me know if you have any questions!

 

Rita Korjonen

Hi Lauren and thanks for helping! I added my comments straight to the review page your link sent me to. But I continue here aswell:

From the article Storyline 360: Definition of Built-In States I found this definition of Disabled state: "Use this state when you want to disable an object. A disabled object is visible to learners, but it won't respond when hovered over, clicked, or dragged. Unless it's the initial state of an object, you'll need to use a trigger to invoke it."

So it seems that there is some kind of bug in Storyline. In my Storyline project (attached to my original message) all the elements have Disabled state but they still do respond when hovered over or clicked.

Phil Mayor

The hover state, iis not really a bug in the disabled state but a bug in grouped objects.

If you ungroup your your objects the disabled state works fine.

As far as the click event, as Michael stated the trigger is on the group not the disabled objects, you cannot disable a group.

It may be better to build one object (you can add objects inside of states) and it will work

Lauren Connelly

Hi Lauren! Thank you so much for your help, this is a really nice way to support with Storyline.

I understand the logic on how the triggers should be set. But I still don't understand why state Disabled doesn't really make the element to be disabled, not able to click? Has something changed with disabled state in Storyline during updates?

From eLearning Heroes I found this definition to Disabled state:

 "Disabled: Use this state when you want to disable an object. A disabled object is visible to learners, but it won't respond when hovered over, clicked, or dragged. Unless it's the initial state of an object, you'll need to use a trigger to invoke it." Link to the article: https://articulate.com/support/article/Articulate-Storyline-360-Definition-of-Built-In-States?_ga=2.214603472.635973891.1564486706-1540193465.1553781197

Hello Rita!

I'm going to respond to your comments on this discussion, just in case anyone else is running into a similar issue.

If you want to fully disable a shape, group, icon, etc., then you need to remove the "hover state".

I'll show you how to do that in this short tutorial!