Forum Discussion
Disabling a text entry field
I have a page with text entry fields. I want to disable / enable fields depending on the value of a variable. Is it possible to enable/disable text entry fields?
37 Replies
Hi Andrew
you could place a transparent (a shape with a fill set to 100% transparency NOT a shape set to NO FILL) shape over the field that is initially in hidden state and then triggered to change state to normal when variable = x value. Once it is normal the user should not be able to click into the text entry field.
Thanks Wendy & Kamil
That's the workaround I have right now, but it seems a bit clumsy to me. Storyline ought to be able to disable text fields based on trigger events
Give some more context Andrew
Do you only want the field disabled when a certain value is entered? or when any value is entered? is it a text entry or number entry? does the user click a button to 'lose focus'.
Perhaps if you upload the slide and give a bit more information on what you want someone might have a different response for you.
No, but you can put on your field f.e rectangle with transparency 100% and user won't be able to click on it.
Hi Andrew,
There isn't a trigger to enable/disable - but you could use the transparent shape over the top of the text entry so that the user couldn't type inside it or click on it. That could be trigger to be in a "normal" or "hidden" state based on the value of a variable when the timeline starts.
If you're still having a difficulty time setting this up please share a copy of your .story file so that we can assist.
Hi Ashley. That's exactly what I'm doing now. But it would be neater and less clunky if I could simply disable text entry - it's a pretty standard web form behaviour - maybe Articulate can add this to the list of nice-to-have enhancements?
Certainly can understand Andrew and I can pass the message along and you can always add ideas here as well.
Hi, since the last 360 update (3.37.21453.0), there is bad behaviour with all the text entry field (text, number).
Even when I put a shape at 100% transparency, I can click on the text entry field, even if I don't see it.
Is anyone else experiencing the same behavior?
Thanks,
Hi Austruy,
Sorry to hear you're coming across odd behavior with the text entry fields! It sounds like you're saying even if you layer a shape on top of a text entry field, you're still able to mouse-click on the text entry and edit?
Do you mind sharing a screenshot or Peek 360 video of what you're seeing?
Hi Ren,
I made some tests, and it appears that the problem is, when the shape is in a layer.
I've contacted the support, using my account. they are working on the bug.
I attached the file so you can see it.
At the left: the "support team" test, at the right: my test whith the shape in a layer.
When I publish I have the problem. I can click on the text entry field.
Hi Aurore,
Thank you for sharing your file! Great call on opening a Support Case as well. I see that Renato is assisting with the Text Entry issue. I am adding your comments to our active report, so we will be sure to provide an update as soon as we have more details to share!
Please let us know if you have any questions!
Hello again, Aurore :)
Great news! We just released another update for Articulate 360, and included a few important fixes that you'll see in the release notes here.
The item you'll be interested in is:Fixed: When the base layer had a data-entry field, interactive objects on other layers weren't clickable and learners could still edit the field on the base layer.
Just launch the Articulate 360 desktop app on your computer and click the Update button for Storyline 360. Details here.
Please let us know if you have any questions, either here or by reaching out to our Support Engineers directly.Hi, I'm having a similar issue with covering text entry fields with a shape. I'm trying to disable text entries in a scrolling panel after the learning types a specific value. Everything works when the objects are outside of a scrolling panel, but it doesn't work when the objects are inside the scrolling panel.
I created a very simple example to show the issue. The example has two text entries in a scrolling panel, and will "hide" the text entry behind a rectangle after entering something in one of the text entries. I gave the rectangle a color to clearly show what is happening. The learner shouldn't be able to change the value in the text entry when the rectangle covers the text entry, but unfortunately, they still can.
You can access the example here: https://articulateusercontent.com/review/items/9w6dGN20qrRu6ucs/story.html
I also attached the .story file to this post.
While covering the text entry with a shape should work, I do think it would be nice to be able to disable a text entry in a different way. Hiding a text entry behind a shape is a workaround, but far from ideal, because it will still be possible to use the Tab key to select the object. I can remove the text entry from the tab order, but that would make it impossible to make a form in a software simulation that actually functions like a form (using tab to jump between text entries).
Hi Mischka!
I'm happy to help! I took a look at your file and made a few changes to create what you're looking for.
Here's what I've done:
- Added a layer and copied the Base Layer content to the Layer.
- Removed the Text Entry Field from the Layer and replaced it with a shape with the text %TextEntry%. This is to show the text without a user being able to edit the entry.
- Added a trigger to Show Layer when the Text Entry field loses focus.
I'll attach the updated project to this discussion.
Hi Lauren,
Thank you for sharing the updated project, I appreciate it!
If I understand your approach correctly, I can use a layer with the same scrolling panel (but rectangles instead of text entries) which covers the base layer after adding a value to the text entry.
I understand how this would work outside of a scrolling panel. But the moment you use scroll and enter a value, the layer appears but reverts the scrolling panel back to its original position (back to top). Which isn't the end of the world, but is unexpected behavior in a software simulation.
And how would this approach work in a form with multiple text entries? Would it require a layer for every possible scenario? To give an example: If I have two text entries. The base layer is for the original state where no text entries are completed. Layer 1 for when the first entry was completed but not the second. Layer 2 for when the second is completed but not the first. And layer 3 for when both of the entries are completed.
As you might have noticed in my example, I'm creating a software simulation where the user is asked to complete multiple text entries in a form, and in any order (the "any order" aspect is very important in this exercise). And most of the forms have a lot of text entries. So to cover every scenario in layers will become harder with every extra text entry in the form.
It's possible that I'm overlooking something in your approach. Excuse me if that's the case.
