I added a disabled state to a slider hoping it cannot be dragged until a variable changes. But it can still be dragged to another step as if this was not disabled at all? If this is what it is, is there another way to prevent the slider from being dragged until a variable changes. I'm doing a crude solution by masking (set to transparent) the knobs and hiding/unhiding the mask based on the variable. It's messy and the change state trigger for the slider would have been more efficient. Thank you for any thoughts on this.
Did you add it to the slider icon element or did you set up a state for the entire thing? Perhaps you could share what you've got set up here so that we could take a look and offer specific suggestions.
I added a disabled stare to the entire thing, meaning the slider just because it was available. I would have wanted to disable just the knob or handle. Did I miss something?
I never had any luck using a disabled state on a slider. You can make it LOOK disabled, e.g. greyed out, but in my attempts it was still draggeable. I resorted to putting a transparent shape over the slider and hide/show that shape depending on some variable value. However, that will not work as long as you are moving the slider, it'll only kick in once you release the slider thumb.
I haven't played a lot with sliders, so was just looking to see more of what you were *attempting* to set up. :) It sounds like Michael's idea will work though.
Thank you for your comments. It was a case of having two adjacent objects, A and B (as in the beads of an abacus). If A were the left-most object, B cannot slide left (Step 1) until A slides left first, otherwise B will be jumping over A. The same conditions exist when sliding back to the right (Step 2), B moves first. The objective was to immobilize the blocked object before the blocking item moves first. Since it was possible to add a disabled state to sliders, I though this was a simple "change-state...when-slider-moves" trigger, that is why I asked the question because the slider still moves even at the disabled state.
I did Michael's idea and it accomplishes the behavior I wanted to achieve. I just had to put up with so many masks to hide/show. I still would have wanted the disabled state though. Thanks once again.
Agree with Michael here disabling a slider is hit and miss, I have achieved once, if you are dragging a slider is seems to be impossible to disable it.
Hi, Rene -- Thanks so much for sharing your workaround here, and you are welcome to share your thoughts or idea with our Product Development team using this feature request form. :)
I know this is an old post, and the workarounds are all great, but the 'bug' as I see it, is still there: disabling the slider with the built-in trigger doesn't work.
We're no longer seeing issues with users still being able to interact with sliders after their states have been changed to disabled. I've attached a sample project file which I used for testing.
Would you mind sharing more details regarding the behavior that you're experiencing so we can check to see if you are still being affected by the same bug discussed in this thread?
Is this still the case? I have a slider on a layer that is hidden but it can still be moved and I need to disable it. Setting the layers to not allow things to be clicked on other layers is not an option so really I need the slider disabled.
I'm happy to chime in! I ran tests on a sample Storyline project using the latest version (Build 3.77.30587.0) and confirmed that hidden or disabled sliders cannot be dragged as expected. I attached my sample project file for your reference.
I just had some clarification questions to understand your experience better:
What Storyline version are you using? Here's how to update to the latest version if needed.
We'd be glad to investigate further if the problem persists. You may share your Storyline project here or privately in a support case so we can look at your setup. We'll delete it when we're done!
I was able to get it working with version SL 3.68.28887.0 (the latest version our organisation has distributed), however there's a small thing I'd like to fix if possible...?
In the attached you'll see that CEO gender can only be changed when Include CEO is On. But it resets to Male each time the layer is unhidden (i.e. when Include CEO is On) instead of resuming from the last option used. I couldn't work out how to get that to resume when I need that slider to be inactive when the layer is hidden and active when it is unhidden.
I think I got it working. I added a text variable that goes from Male to Female as the second slider moves. This could have easily been True/False or 0/1 variable, but I did that way so I did not confuse it with existing ones and could easily see what the value means (I just couldn't remember if 1 meant male or female). That reference box is there just I could see the value, and it can be deleted.
Then I added triggers that checked the value of that new text variable and adjusted the state and position of slider accordingly when it appears.
Now there are quite a lot of triggers for fairly a simple feature, so there might easier way to all that. But I did it with "Add stuff until it works" -method.
Just realised that the text variable was totally unnecessary, as the slider position variable already exists and it can used to make sure that the state and position of the slider is correct. But like I said, is usally use "Add until it works", and sometimes I add more stuff that what is needed.
Brilliant! Thanks Tommi - you've solved it! I really appreciate it!
I too am a fan of the 'add until it works' method. The ability to enable and disable triggers without deleting them is a feature I'm really pleased exists.
21 Replies
Hi Celito,
Did you add it to the slider icon element or did you set up a state for the entire thing? Perhaps you could share what you've got set up here so that we could take a look and offer specific suggestions.
I added a disabled stare to the entire thing, meaning the slider just because it was available. I would have wanted to disable just the knob or handle. Did I miss something?
Sent from Yahoo Mail on Android
I never had any luck using a disabled state on a slider. You can make it LOOK disabled, e.g. greyed out, but in my attempts it was still draggeable. I resorted to putting a transparent shape over the slider and hide/show that shape depending on some variable value. However, that will not work as long as you are moving the slider, it'll only kick in once you release the slider thumb.
Hi Celito,
I haven't played a lot with sliders, so was just looking to see more of what you were *attempting* to set up. :) It sounds like Michael's idea will work though.
Hello Ashley and Michael,
Thank you for your comments. It was a case of having two adjacent objects, A and B (as in the beads of an abacus). If A were the left-most object, B cannot slide left (Step 1) until A slides left first, otherwise B will be jumping over A. The same conditions exist when sliding back to the right (Step 2), B moves first. The objective was to immobilize the blocked object before the blocking item moves first. Since it was possible to add a disabled state to sliders, I though this was a simple "change-state...when-slider-moves" trigger, that is why I asked the question because the slider still moves even at the disabled state.
I did Michael's idea and it accomplishes the behavior I wanted to achieve. I just had to put up with so many masks to hide/show. I still would have wanted the disabled state though. Thanks once again.
Agree with Michael here disabling a slider is hit and miss, I have achieved once, if you are dragging a slider is seems to be impossible to disable it.
Thanks Celito for sharing the update - and I'm happy to hear you've found a method to make it work, even if it wasn't ideal.
Hello everyone,
I have just had the same issue with a slider being in the state "Disabled" but still draggeable. What I did as a workaround:
I replaced the slider with an image of the slider and with some triggers I reached my goal:
1) User drags slider to certain value and receives either feedback right or wrong.
1) a) On the start page, the image of the slider has the state "Hidden".
2) On the feedback layer, the user clicks a cross to close the feedback panel.
2) a) When clicking the cross, I trigger the following two things:
--> Change state of "Slider" (the slider itself) to hidden
--> Change state of "Slider_grahic" to normaö
Thus, the user cannot drag the slider any more when returning from the feedback panel.
Hope this helps / inspires:)
But anyway, it would be more then useful if the slider would really be disabled, when the state is "Disabled".
Would this be some sort of a feature request?
Regards
René
Hi, Rene -- Thanks so much for sharing your workaround here, and you are welcome to share your thoughts or idea with our Product Development team using this feature request form. :)
This was a brilliant idea
I know this is an old post, and the workarounds are all great, but the 'bug' as I see it, is still there: disabling the slider with the built-in trigger doesn't work.
Hi, Stephen.
Thank you for reaching out!
We have a bug reported where the Slider's disabled state is not working.
I've connected this discussion to the bug report, and I'll be sure to come back to update you when I have some news.
Hello Everyone!
I have some great news to share. We just released another update for Storyline 360. In Update 74, we’ve included important fixes and new features.
One of the bugs that was fixed was an issue which caused the slider disabled state to not work properly.
To take advantage of this update, launch the Articulate 360 desktop app on your computer and click the Update button next to Storyline 360. You'll find our step-by-step instructions here.
Please let me know if you need additional help!
Hi Joe,
I updated my Storyline and am still receiving this error with the disabled state of the slider. Any suggestions?
Thanks!
Hello Alicia,
We're no longer seeing issues with users still being able to interact with sliders after their states have been changed to disabled. I've attached a sample project file which I used for testing.
Would you mind sharing more details regarding the behavior that you're experiencing so we can check to see if you are still being affected by the same bug discussed in this thread?
Is this still the case?
I have a slider on a layer that is hidden but it can still be moved and I need to disable it. Setting the layers to not allow things to be clicked on other layers is not an option so really I need the slider disabled.
Hi Kevin,
I'm happy to chime in! I ran tests on a sample Storyline project using the latest version (Build 3.77.30587.0) and confirmed that hidden or disabled sliders cannot be dragged as expected. I attached my sample project file for your reference.
I just had some clarification questions to understand your experience better:
We'd be glad to investigate further if the problem persists. You may share your Storyline project here or privately in a support case so we can look at your setup. We'll delete it when we're done!
Thanks Eric,
I was able to get it working with version SL 3.68.28887.0 (the latest version our organisation has distributed), however there's a small thing I'd like to fix if possible...?
In the attached you'll see that CEO gender can only be changed when Include CEO is On. But it resets to Male each time the layer is unhidden (i.e. when Include CEO is On) instead of resuming from the last option used. I couldn't work out how to get that to resume when I need that slider to be inactive when the layer is hidden and active when it is unhidden.
Hope this makes sense.
Many thanks,
Kevin
I think I got it working. I added a text variable that goes from Male to Female as the second slider moves. This could have easily been True/False or 0/1 variable, but I did that way so I did not confuse it with existing ones and could easily see what the value means (I just couldn't remember if 1 meant male or female). That reference box is there just I could see the value, and it can be deleted.
Then I added triggers that checked the value of that new text variable and adjusted the state and position of slider accordingly when it appears.
Now there are quite a lot of triggers for fairly a simple feature, so there might easier way to all that. But I did it with "Add stuff until it works" -method.
Just realised that the text variable was totally unnecessary, as the slider position variable already exists and it can used to make sure that the state and position of the slider is correct. But like I said, is usally use "Add until it works", and sometimes I add more stuff that what is needed.
Brilliant! Thanks Tommi - you've solved it! I really appreciate it!
I too am a fan of the 'add until it works' method. The ability to enable and disable triggers without deleting them is a feature I'm really pleased exists.