Forum Discussion
Remove zero from Numeric Entry field
Hi
I am using Storyline 360 and have an issue with the Numeric Entry box being populated by a zero when the slide starts. I have Googled this issue but every discussion is over 5 years old. Has there ever been a fix for this? I want the box to be blank when the slide starts, not have the user continually delete the zero before entering their value.
Many thanks
25 Replies
- Jürgen_Schoene_Community Member
to create a variable for a numeric input field is a little bit special
- BrianBland-ClarCommunity Member
yes please fix this bug. storyline is horrible about the timeliness of fixing problems.
- MichaelHartman-Community Member
I have currently run into this issue. Is there an update on when this will be fixed?
- BrianBland-ClarCommunity Member
This is Articulate, not Google. They don't fix problems here, they just let us rant about them for years knowing they can charge us $1k/yr and then give platitudes of customer service...
- MartinGregsonCommunity Member
Is there any chance Articulate could give us, the people who pay their salaries, an idea of how bugs are prioritised? It appears that the system in use at this moment is not working,
PS. not that I am expecting a reply (Prove me wrong)
Hi Martin!
Thanks for checking in on this and sharing your feedback!
This article goes into more detail on how we tackle bugs. I don't have any updates to share at this time as our team has been prioritizing other fixes, but I've included your notes in the bug report and will update this discussion as soon as we have news to share.
We appreciate your patience and apologize if this issue has been slowing you down!
- BrianBland-ClarCommunity Member
Apologies but this is laughable at best. This bug has been present for literally 5+ years and it hasn't been addressed. This objectively means you do not care.
- AndresBowenCommunity Member
Hey Everyone! I found out a way to get around this issue. Works for me, hopefully for you too. If I set up a brand new numeric entry in the Base Layer (hope that's the name in English!) when I run the slide there is a zero in the box. BUT if I create it on an additional layer, the exact same one (even copying and pasting the original), the box looks empty upon running the slide, no famous zero in sight. (I'm from Chile, apologies for the Spanglish!). All the best! Andres.
- SarahSamzCommunity Member
Hello, I am also encountering this issue. I have a large number of text entries in my course. This would be a helpful fix so the learner does not accidently forget to delete the zero and receive a fail when submitting.
- RebeccaSaund790Community Member
I have a work around which is not as good as a bug fix, but it did the trick.
- Create your first numeric entry as a "throwaway" entry. Let Articulate name it and the variable whatever its default is. (This was necessary for my use case because I have numeric entries on several slides in several stories, so I don't want the default name change to potentially impact other triggers code.)
- Make copies of that numeric entry. You can rename the numeric entry box in the timeline and rename the variable in variables. (This is not ideal. I had already established my variables and had to delete those to rename the new ones so my JS code would work, but that was my simplest workflow.)
- Delete or hide the throwaway entry. (Don't delete the variable, just hide or delete from the timeline.)
- zamond1Community Member
I'm experiencing something similar. I have a numeric input field, titled "capture savings" and, separately, I have a number variable named "savings". The trigger on "capture savings" is:
When capture savings loses focus
- Set savings equal to the typed value
When previewing, there is a leading zero in "capture savings," which you manually have to backspace to get rid of. I have several other similarly set up capture fields with corresponding variables on the same slide. Am I going to have to jump through hoops to deal with this? It sounds like this has been an issue 5+ years now...
- AndrewBlemings-Community Member
Hi zamond. I wonder if the issue is simpler than people think, and may accidentally betray people's misunderstanding of an otherwise rational system. It's not really my vehicle's fault if it doesn't drive a way it wasn't designed to, but rather my "issue" in that example comes from my misaligned expectations.
What is the default value of the capture savings variable? Because if its default is the zero it was created with, the standard for numerical variables, then that's what shows when I load the slide each time. Maybe you can share a project file?
Related Content
- 20 days ago
- 7 months ago