multiple random fill-in the blank questions

Hi Joe,

I think a lot of people have been in your shoes before... so many triggers and variables, and it feels like the solution is right there!

Would you be open to sharing a few slides or the whole project? I think I understand what you're trying to do, but would like to tinker and test my theory before we add any more triggers or variables. You can post the file here or PM me. Thanks.

Hi Luke,

thanks for replying so quickly. I'm tempted to send you the whole file, though, is there a way I can post it to you directly rather than in this forum? By the way, what do you mean by PM? (sorry!)

Thanks

Yes, I think you mean private message. I haven't yet worked out how. :-| (embarrassed face)

No worries Joe.

If you click on my profile icon, it will take you to my profile page with a "Contact Me" link. You can use that to send either a share link from DropBox/Drive/S3 or the whole file if it's small enough.

Hi Luke

Thanks for doing this for me.

I have made a copy of the Storyline slide in question (see attached). What I am trying to do is being able to fill the field boxes with the below items. All can be inserted in whichever order one wishes, and bullets 1 and 7 have more than one possible option. Once the user enters the full list, they get a 'correct' feedback, and 'incorrect' until they type all the correct items. It sounds a bit long winded but I'm just trying out so I can show one of our academics what can be achieved in Storyline, and whether this type of quiz is workable or not.

Many thanks for your valuable help.

Kind regards
Joe

* Legal place / seat / venue

* reference to rules of arbitration institution

* Governing law of the contract

* Language

* Number of arbitrators

* Qualifications of arbitrators

* Escalation from mediation / tired dispute resolution clause

* Expedited procedure

* Confidentiality

* Selecting and replacing arbitrators

* Scope of disputes covered

Institute for Teaching, Innovation and Learning (INSTIL)
University of West London
BY.03.019
St Mary's Road
Ealing
London
W5 5RF

T: +44 020 8209 4130
E: joe.turi@uwl.ac.uk
Fire Marshall

For any information on what INSTIL can offer you or your School please visit http://www.uwl.ac.uk/instil/instil
INSTIL events: http://www.uwl.ac.uk/instil/events

[cid:image002.jpg@01D257A2.C59E2580]

By the way, you can ignore the triggers 'Change state to' taking to other questions (as you see they appear unassigned).

Joe

Hi Joe,

I did not see an attachment. Can you send an email to luke.benfield@gmail.com? Thanks.

Hi Joe - looks like you may be replying to the forums via e-mail. That would explain why your attachment did not make it through and why we are seeing your signature. You are welcome to pop in and edit if needed.

Thanks for all the assistance you've been providing in the forums Luke :) It has not been unnoticed.

Ok Joe. Everything is fixed. I'll send you the file via email.

For the good of the discussion thread, we had a couple of issues and solutions:

Issues - 

• Triggers fire in order from top to bottom, and in this course, there were triggers that were too far down on the list for the ones at the top of the list to catch. Example - having the state change trigger of the Correct button being on the list above all the Correct variable adjust triggers.
• Another thing I discovered was a classic case of the rabbit hole (happens to everyone...) where there were too many variables, and variables being triggered to do things that weren't actually there. Example - the Box#Correct variables had conditions based on what were supposed to be the text entry variables, but the text entry variables were all empty because the text entry boxes were sending the information to a whole different set of variables.
• When creating the basic variables for the text entry boxes, the default value was set with the actual answers, so if everything had worked, the answers, technically, would have already been filled in - those default values should be blank.
• All of the Box#Correct variables needed to be changed from being connected to the submit button, to being based on when each Text Entry Box variable adjusts.

Solutions:

• When you have this many variables in the works, I find it best to create text boxes and create variable references (putting percent symbols before and after the variable name with no spaces) to call the variables on screen. This way, you can see what is happening to the variables in Preview mode, and help diagnose where the glitches are happening. 
• Double check the order of your triggers. Example - you wouldn't want a Jump To trigger on your list above a variable change because it may change slides before the variable actually changes.
• Objects that you have off-stage (off-screen) to run in the background should be brought on screen for testing so you can see if everything is working properly. When it all works, move it back off-screen.

Happy to help Leslie.

So very thorough - thanks again Luke :)

Hello Luke,

Thanks for providing a detailed list of the issues and the solutions. I was able to download a trial version of AS2 in an emergency laptop I found (problems with my current work PC and our IT department's restrictions with permissions on staff equipment, but let's not go there). So, once I got my head round to make sense of it all, I understood I had to rectify the basic variables for the text entry boxes where I ended up writing in the answers, instead of leaving them empty. In addition, I made a mistake of connecting all the variables for each field box to link with the submit button. Of course, I instead needed to reassign as 'when the variable changes to' its corresponding Text Entry field box (that I have created in my template where the various answer options will be typed in by the respondent).

I have also noted that when creating these many variables, one needs to be careful in respecting the top to bottom order. Though, I realize this will take a lot more practice to grasp it completely.

I found your suggestion to create text boxes for the various answer fields with variable references in them, displayed on the layer temporarily, as very useful when testing the behavior of the variables on screen. Really great tip!

Thank you so much for your invaluable time and assistance with this.