I like to use variables to drive navigation in my courses - for example, having tasks that trigger variables when complete, send the learner to a 'well done' page.
Often I make a mistake in the variables so the navigation doesn't work as planned. I then have to go through all the variables to isolate the problem.
Has anyone developed a checklist or process to make this less painful and boring? How do others deal with checking variables?
One thing I like to do is to use variable references in a text box. I use this so I can monitor the behavior of my variables. I only do this for the trouble shooting, and I delete this text box once I'm finished. If the interaction involves multiple slides, then I paste this text box over each slide. I've attached a demo of what I'm talking about.
In this file, the user must select both switches to enable the next button. If the user unselects a button, then the next button is disabled again. To make sure my variables are performing as expected, I have a text box on the slide that shows me what is going on "under the hood".
It helps to use very descriptive names for the variables. You are unlikely to misuse a variable named SlideOneCompleted, or SelectingCorrectDateCompleted, or ReadyToAdvanceToQuizOne.
Similar to Preston's and Walt's suggestions, I use descriptive variable names and reference them in a text box. During development, I usually put that textbox on the masterslide and use a keypress trigger to show/hide the textbox. That way I can check the content of variables any time.
4 Replies
One thing I like to do is to use variable references in a text box. I use this so I can monitor the behavior of my variables. I only do this for the trouble shooting, and I delete this text box once I'm finished. If the interaction involves multiple slides, then I paste this text box over each slide. I've attached a demo of what I'm talking about.
In this file, the user must select both switches to enable the next button. If the user unselects a button, then the next button is disabled again. To make sure my variables are performing as expected, I have a text box on the slide that shows me what is going on "under the hood".
Hope this helps!
It helps to use very descriptive names for the variables. You are unlikely to misuse a variable named SlideOneCompleted, or SelectingCorrectDateCompleted, or ReadyToAdvanceToQuizOne.
Similar to Preston's and Walt's suggestions, I use descriptive variable names and reference them in a text box. During development, I usually put that textbox on the masterslide and use a keypress trigger to show/hide the textbox. That way I can check the content of variables any time.
Wow... I like the keypress trigger idea. Smart idea
This discussion is closed. You can start a new discussion or contact Articulate Support.