Disabled state
Aug 23, 2016
Ok, this is the BEST place for help!
I am having trouble with the disabled state.
So just a little about what I am doing....students will be clicking on a text box (normal state) and going to another slide.
When they finish reviewing that slide they are prompted to go back to the homepage where I want that text box that was just clicked to be disabled.
When I seem to add in that trigger, it does not disable, as in I can still click on it and it goes back to that slide.
I have other states which is where I might be running into some problems.
There is a "Hover state" that simply changes the color of the text.
I also have a "Visited" state that changes to grey color to show they have already been there.
So the problem now is, when I create the disabled state, they can still click on it (and I do not want them to be able to do that)
All in all, my states:
Normal
Hover
Visited
Disabled (the problem state)
Anyone else ever have this issue??
Thanks in advance!
Heather
23 Replies
Hi Heather- Would you be able to share your .story file so we could take a closer look? You can add it in a comment right to this thread by using the "Add Attachment" option.
I have the same problem with the disabled state. It is still clickable when it is disabled.
I wunder what the solution of the problem of Heather was.
If you have created your own disabled state (like it appears that Heather did), it probably won't work the same as the built-in disabled state.
We used the built-in state and didn't create our own.
Hey Josien! I'm not sure what Heather's resolution was here, but you're more than welcome to share your .story file here in a comment! I'd be happy to take a look and see if I can spot what's happening.
Hi, I am having a similar problem. I have created 3 states: normal, hover, and disabled. I set my initial state to disabled on my slide, but when I hover over it, it still shows me the hover state. Should the hover be disabled in the disabled state? Thank you!
Hey Marina! If your initial state is disabled, the hover state shouldn't be showing. I made a quick example of this to test it out which I've attached here for reference.
Would you be able to share your .story project file so I can take a look at your current setup?
This post was removed by the author
It's about the layer 'witte balk uitklap'. The trigger 'jump tot 3.1. hoofdstuk 2.1 works already when this item is disabled.
Hey Josien-- Thanks for sharing your file here! I see what you're saying about the "Jump to" triggers still working despite the state being disabled in the dropdown menu on that layer. I went ahead and set up a case with our Support Engineers to investigate this a bit deeper with you. Your case number is 01040377 and one of our Engineers will be reaching out to you shortly via email. I'll be keeping an eye on it too, as I'm curious what the cause could be here!
Hi Ali and Josien,
Thank you very much for sharing these examples with me! I am going to check it out and then if I continue having problems, I will definitely post the .story file! Thanks for your help!
Sounds great, Marina! Be sure to keep us posted :)
The solution for my problem is to use a shape instead of a text box.
Ah! Thanks for sharing that update here, Josien. I'm glad it's working for you now :)
Having the same issue in storyline360. When the user clicks on a button I have a trigger to change the state of another button to disable. But when you revisit the slide ( I have resume saved state for that slide) the disable state is still select-able.
Hi Jack
can you share the .story file - I'm not seeing that behaviour - see Peek video of rough sample
and here is the .story file sample
Hi Wendy sorry for not responding back. I figured out the issue it was the order in which I had my triggers that was causing the issue.
Glad you got it sorted Jack - all the best with your project :-)
I'm also experiencing trouble with the disabled state.
The Continue button begins in the disabled state and triggers change it to the normal state after the learner has clicked both of the red canisters in the bin under the table.
However, before both canisters have been clicked, I can roll over the Continue button and click it. If I click it, it changes its appearance from greyed out to what appears to be an active/available state, which would be rather confusing to learners since it apparently isn't active (clicking it does not activate the Jump to next slide trigger).
Shouldn't setting the button state to Disabled make the button unclickable altogether?
I've attached a 2-slide *.story file.
Thanks.
-Ray
Forgot to say I'm using Storyline 360.
Hi Ray
see attached Peek video - I'm seeing a hover hand display when you hover over the white rectangle - could be something funky with that group of objects.
Hi Wendy,
Yeah, that's Storyline's unfortunate habit of extending the effective size of a button's hotspot to encompass the surface area of every object the button is grouped with. In order to have the fly-in animation on that instruction panel bring all the elements onto the screen together, the step number ("2"), the panel, and the Continue button are all grouped together (e.g., I selected them all and grouped them with control-g, and then applied the fly-in animation to the resulting group).
I have done this so often I almost stop noticing how wrong it is that rolling over any part of the group is treated like rolling over the button in the group. :-)
However, the group seems to be the source of the problem with the disabled state, so thanks for bringing it to my attention. If I ungroup the button, the disabled state works correctly. When grouped, it does not.
Looks like a Storyline bug to me.
Thanks!
-Ray
UPDATE: I submitted a case with the support team.
Hi Ray,
Thanks for reaching out to the support team.
I see that Anna was able to pop in and assist you and it seems your suspicions were right.
Thanks Leslie!
Yes, the Articulate support team is on the case. :-)
Cheers!
-Ray
This discussion is closed. You can start a new discussion or contact Articulate Support.