Forum Discussion
How to remove an initial value (0) from a "Numeric Entry" field
Hello,
Can anyone know, how to remove an initial value i.e. 0 from a "Numeric Entry" field?
Thanks in advance....
74 Replies
- talshenkarCommunity Member
Hi , I also need this update on Storyline3, it's very urgent!
- katiaborkovCommunity Member
Hello,
In our company we would like to have an option to use numeric enteries which doesn"t show any placeholder content (now its 0 there by default which is a problem cause we teach math).We are using Storyline 3
Thank you,
best regards. - valeriabaron-71Community Member
Hello, I have also encountered this problem several times, I have had to look for other creative ways that have not worked either (through a JavaScript trigger), this currently creates a poor user experience for users because users need to solve exercises in math and when I show them that a certain exercise is equivalent To 0 I am presenting something wrong pedagogically. I need the text box to be completely empty. I would be happy if you could help with this issue when you release the next version of Storyline 3 as soon as possible, a large amount of what I do is done in numerical text boxes. Hi all,
I can understand how important this fix is for you, and we'll let you know here as soon as it's ready for Storyline 3. You'll also find that information updated in the Storyline 3 version history once the update is ready.
- orditcohen-75c8Community Member
Hi Ashley,
As you can see, this discussion is from 5 years ago, and people are still complaining.
Until now, articulate only released a fix for storyline 360, although storyline 3 Exist before 360 and we all have this problem for several years.
if articulate already found a fix for 360 so i guss its the same fix for storyline 3.
We would really appreciate if articulate can fix it as soon as possible and release an update.
Thank you.
Hi Or,
Storyline 360 will always be the latest, most up-to-date version and you can see the release history for our latest build 3.28.18944.0 here. We’re continuing to support Storyline 3 with bug fixes, but we aren’t adding any major new features to Storyline 3 or sharing a release schedule.
The issue that occurred and the subsequent fix in Storyline 360 and Storyline 3 was a bit different than in Storyline 2 due to the difference in how each of the authoring tools is structured.
Once the next update of Storyline 3 is ready, we'll post here to let folks know!
- Hi all!We just released Update 7 for Storyline 3! (Build 3.7.20003.0) 🎉Remember the issue where numeric-entry fields displayed default values of zero after renaming their underlying variables? In update 7, the numeric- entry fields will remain blank until learners enter values.
Hi Brian,
Thanks for reaching out, and I'm sorry you are facing this!
We released a fix for this problem in Storyline 360 Update 28 and Storyline 3 Update 7, but I'm happy to explore further!
I'm having trouble recreating the zero value in a numeric-entry field in a sample Storyline 360 Update 41 slide. Here's a quick recording of the test.
Are you comfortable with sharing your slide so I can try to replicate it? You can use this private upload link.
- StevenWalsh-711Community Member
I had this happen to me as well. Looking over the history of this issue, I found out why. Alyssa Gomez, 2 years ago: "This is happening because there is a bug in Storyline 360 where when you rename a numeric variable, the entry field and the variable reference display a 0 instead of the default blank."
My solution is to return the numeric variable to the input field, then create a second trigger that sets my variable to the numeric variable when the input field looses focus.
- ChrisDickste585Community Member
I know this has been discussed for a few years but wanted to see if there was any progress.
Is there a way for the numeric entry field to go back to being blank after a user clicks the reset button i added? I can only set it to zero, however i would prefer to have it be blank when reset.
- MikeAdamskiCommunity Member
This still seems to be a bug. Any update on this?
Related Content
- 11 months ago