data entry boxes need normal/hidden states
Jul 17, 2012
I don't know if this is a feature that can be changed or not, but it would be nice to have the ability to show/hide a data entry box. I'm creating a project where the learner will select an applicable appliance, enter the BTU and have the course add up the total. Once the data entry box for the BTU is displayed (I have each one on its own layer, but that's not the issue), there is no way to "reset" the slide so that the data entry box does not show.
If this can be changed to allow show/hide states like other objects, that would be very helpful, thanks.
14 Replies
Hi Laurel, I cannot understand, you can hide and show layers at will if they have data entry field on or not. can you post the slide and I am happy to have a look.
My apologies. I have since discovered that I have to make the checkbox state to "not Selected" instead of "is Normal" for this to work. I was having an issue hiding a data entry box on a layer by hiding the layer -- I thought the fact that the data entry box doesn't have states was the problem. Sorry for the confusion. Thanks.
In the attached example, the first one, Central heater is set to hide layer when state of checkbox is Normal. The second one, Dryer works when the state of checkbox is set to not Selected. Who knew there was such a big difference and that it doesn't hide the layer on the other states! =0
Hope this is the right place to post this, but seems to be close to what I'm looking for and I can't find other references. I need to have the user enter data in 7 separate text data entry fields on a form on a single slide layer. I want a 'Continue' button to appear only after all data entries have been made. To do this, I'd need the data entry fields to be assigned 'visited' or 'selected' states, but unable to assign states to them like I can with a normal text box. Is there another way to do this?
You dont need a state to do this you could set a trigger based on the variable value, You could use change state of continue button to normal (from hidden) when variable adjusted, with 7 conditions that variable1, 2, etc not equal to null (leave the value blank, if they are numbers choose 0).
Thanks, Phil.. looks like I've got some studying to do with variables. I'll give that a try.
Hmmm...created 'varcomplete' and set 'varcomplete' = false. Set 'varcomplete'=true when text entry ACNO is NOT=NULL. Gave button initial condition 'hidden' and trigger to 'normal' when 'varcomplete' changes from false to true. OK- that works, but as soon as I add the second text entry field 'datez' condition also NOT=NULL for 'varcomplete'=true, the button stays hidden even when both fields are NOT=NULL. Remove the 'datez' NOT=NULL condition from the list and it works again.
Hi Jeff, sorry did not explain myself to well, those text entry fields are already attached to variables, I will posts a demo for you, will try and do a screenr if I get time
Phil
Hi Jeff
Try this, if you need a screenr let me know, its done with three triggers and no addition variables
Phil
OK- I see that have to create 9 separate triggers- one for each field on my form. I was trying to create a trigger using one variable that conditioned all of them to be NOT=NULL. Let me try it your way. Thanks for working with me!
Jeff, dont forget you can copy and paste triggers, then just change the variable it references and the condition, much faster
Right... can you tell me what the problem is with my logic regarding creating a true/false variable that changes to true IF ALL of the textentry fields are NOT=NULL? I think if I understand that, I can slink away into the night and lick my wounds.
Thanks again!
OK, I will try. When looking at triggers they only fire because something is happening e.g. when clicked, when timeline starts etc
The only one that is actively listening is the when variable changes.
In your example you could also use when control loses focus.
If you want to use the T/F example it will work but you will need a trigger on each text box, for either control loses focus or variable changes to fop the T/F to T with conditions for all the other textboxes. You would then need a trigger to change to continue button from hidden to normal. So in your example you have 1 more trigger and 1 more variable. There is nothing wrong with this, and it would work, I just think my way was more elegant
So in reality nothing wrong with your logic, I just approached it a different way (I also built a much simpler example)
Storyline is great that there are many ways to skin a cat!
Right on all counts... including the elegant thing. Your responsiveness is most refreshing, so again..many thanks!
Happy to help, I learnt something as well, I had never tried to do that before so it was a nice challenge
This discussion is closed. You can start a new discussion or contact Articulate Support.