I need to simulate the little dots that appear in place of alphanumeric characters when a user enters a password. I could put each dot in a layer that would be triggered by typing. The Trigger Wizard would read:
Action = Show layer
Layer = Dot1 (Dot2, etc.)
When = User Presses a key
Key = [Unfortunately, I don’t know which key!]
Is there a way to enter a wildcard in the “Key” field that would respond to the user pressing any key? If not, can anyone think of a way to simulate entering a password?
You could have the user click buttons to put in their password and then put a hotspot over the whole button bank that would be the actual click region. That way, no matter what button the user thought they clicked on they would actually be clicking on the hotspot; making your dot layer much easier to manage.
Although, this would only be a solution if you didn't care what password they entered.
The information on the text entry and variable fonts is documented here. Those fonts can't be embedded in the content such as they are on the slide - so the user would need to have those fonts installed - if it ends up that they don't, it'll default to the system fonts.
I know this is a really old thread, but I have a similar need and I haven't found an answer yet for how to use any key for these kinds of things.
My need is that i want to change the state of a button to visible if a user types anything at all in the last text entry field. I want to force them to type something - anything, even if it's just a single key. So neither the trigger "when user clicks on text box" nor "when text box loses focus" will do - the former because it doesn't force typing something and the latter because it forces the user to click somewhere after the last text field and they might not. So, typing any key will do and i'd prefer not to have to make a trigger for every key on the keyboard...
Based on your requirement, it appears that you need another trigger event that can be assigned to 'Set text entry' action. Unfortunately, text entry boxes can only assign values to variables after losing focus on the input box. I'd recommend raising this as a feature request to let our product team know that you're interested in this feature! Here's a quick look at how we handle feature requests.
Douglas Spencer's idea might work for you. Put one hotpsot over the keys, and a second over the Enter key. Use a regular text box (or rectangle) instead of an input box, and show a layer with a dot (or change the state) for every click until Enter is clicked.
9 Replies
You could have the user click buttons to put in their password and then put a hotspot over the whole button bank that would be the actual click region. That way, no matter what button the user thought they clicked on they would actually be clicking on the hotspot; making your dot layer much easier to manage.
Although, this would only be a solution if you didn't care what password they entered.
There was a lengthy thread a while ago, that discussed options to simulate a password field. See here: https://community.articulate.com/discussions/articulate-storyline/help-creating-a-password-field
The suggestion to use a font with all dots made it really easy.
2 things:
Hey John,
The information on the text entry and variable fonts is documented here. Those fonts can't be embedded in the content such as they are on the slide - so the user would need to have those fonts installed - if it ends up that they don't, it'll default to the system fonts.
I know this is a really old thread, but I have a similar need and I haven't found an answer yet for how to use any key for these kinds of things.
My need is that i want to change the state of a button to visible if a user types anything at all in the last text entry field. I want to force them to type something - anything, even if it's just a single key. So neither the trigger "when user clicks on text box" nor "when text box loses focus" will do - the former because it doesn't force typing something and the latter because it forces the user to click somewhere after the last text field and they might not. So, typing any key will do and i'd prefer not to have to make a trigger for every key on the keyboard...
Hello,
Based on your requirement, it appears that you need another trigger event that can be assigned to 'Set text entry' action. Unfortunately, text entry boxes can only assign values to variables after losing focus on the input box. I'd recommend raising this as a feature request to let our product team know that you're interested in this feature! Here's a quick look at how we handle feature requests.
Thanks! :)
O&SD,
Douglas Spencer's idea might work for you. Put one hotpsot over the keys, and a second over the Enter key. Use a regular text box (or rectangle) instead of an input box, and show a layer with a dot (or change the state) for every click until Enter is clicked.