The slide I need help with is called "Other (edit to pass)". (fyi, the real menu will not show any slide names)
The goal is to have the learner explore the screens, find the modified text (blue) and clear out each text box. (LOL, they can just click delete from the first slide, but some learners will do it this way)
I imagine I would have some script pass them on to the "question complete" slide if each box is "null" (empty) - or - they could fill out the fields and press a submit button?
- However I have been using "3 attempts" as a limit, so perhaps both methods should be used. "submit" if they do not enter it properly, to trigger the "try again" counter and display the "try again" layer (potentially resulting in a "3 attempts" fail layer), AS WELL as a script that just automatically passes them on to the "question complete" slide if they clear them all out.
Unfortunately, I can't open your file as I guess I don't have the latest version that supports expanded quiz tracking and track multiple completion criteria.
First step is use real input fields. In your version it were no input fields so you cannot change much.
So i added 2 variables. %amountEmptied% and %isAllEmpty% When emptying a input textfield i add 1 to the amountEmptied. A check if amountEmptied > 15 will do for the final check..
Not ready yet, but this will help you ahead for sure...
If you have trouble getting the rest done, let me know and i help.
You do need these 4 triggers on each inputfield ( at least with my approach )
-Offcourse setting the value of the Entry variable ( i renamed them to 2020val because i like good readable variables instead of Entry_001 etc. )
-Then adding 1 to emptiedAmount...if the users clears the inputfield.. -Then subtracting 1 from emptiedAmount to make sure he doesnot enter something again..., you could block or remove that inputfield too...
-then checking whether the emptiedAmount >= 8 and if so, set isAllEmpty to true...
Noticing some errors in this approach now.. If a user removes not all but a single character from the inputfields...well the count goes to -1 and it doesnot work properly...gonna fix that somehow ;-)
In fact its basic logic whats needed to do something like this. Just start writing down in plain text what you want to happen, then find the needed triggers to get that done. Variables in Storyline are important...read anything about it you can find. One important thing to remember is order of triggers in Storyline. They happen sequentially from top to bottom, so if you have something downbelow it might never get there if a upper trigger goes to the next slide ;-)
Here is the fixed and working setup for your project.
9 Replies
Can you share the file?
At first thought, it would have to be a text entry field for each one, each with it's separate variable to test to see that it is blank at some point.
Here is the scene exported separately.
The slide I need help with is called "Other (edit to pass)". (fyi, the real menu will not show any slide names)
The goal is to have the learner explore the screens, find the modified text (blue) and clear out each text box.
(LOL, they can just click delete from the first slide, but some learners will do it this way)
I imagine I would have some script pass them on to the "question complete" slide if each box is "null" (empty) - or - they could fill out the fields and press a submit button?
- However I have been using "3 attempts" as a limit, so perhaps both methods should be used. "submit" if they do not enter it properly, to trigger the "try again" counter and display the "try again" layer (potentially resulting in a "3 attempts" fail layer), AS WELL as a script that just automatically passes them on to the "question complete" slide if they clear them all out.
Unfortunately, I can't open your file as I guess I don't have the latest version that supports expanded quiz tracking and track multiple completion criteria.
Maybe someone else can take a look and help out.
Let me try to export to an older version. update : Look's like I cant :-(
First step is use real input fields. In your version it were no input fields so you cannot change much.
So i added 2 variables. %amountEmptied% and %isAllEmpty%
When emptying a input textfield i add 1 to the amountEmptied. A check if amountEmptied > 15 will do for the final check..
Not ready yet, but this will help you ahead for sure...
If you have trouble getting the rest done, let me know and i help.
Kind regards,
Math
You do need these 4 triggers on each inputfield ( at least with my approach )
-Offcourse setting the value of the Entry variable ( i renamed them to 2020val because i like good readable variables instead of Entry_001 etc. )
-Then adding 1 to emptiedAmount...if the users clears the inputfield..
-Then subtracting 1 from emptiedAmount to make sure he doesnot enter something again..., you could block or remove that inputfield too...
-then checking whether the emptiedAmount >= 8 and if so, set isAllEmpty to true...
Noticing some errors in this approach now..
If a user removes not all but a single character from the inputfields...well the count goes to -1 and it doesnot work properly...gonna fix that somehow ;-)
Wow. thanks! yea the original text boxes were just placeholders for whatever solution ends up being used. but wow. i really appreciate the help!
I would like to ask how do i learn scripting / triggers like you are using. It would be nice to know how to do what your doing.
In fact its basic logic whats needed to do something like this. Just start writing down in plain text what you want to happen, then find the needed triggers to get that done. Variables in Storyline are important...read anything about it you can find. One important thing to remember is order of triggers in Storyline. They happen sequentially from top to bottom, so if you have something downbelow it might never get there if a upper trigger goes to the next slide ;-)
Here is the fixed and working setup for your project.
Perfect Thanks! sorry i was on Vaca for a few days.
I will study this and how it functions so i can understand variables better.
This discussion is closed. You can start a new discussion or contact Articulate Support.