- Quick Win Tutorials
- Getting Started
- Modular Development (ModDev)
- Quick Guides
- Navigating the Workplace
- Building a Title
- Importing Content
- Working With Text
- Working with Images
- Working With Objects
- Actions and Variables
- Tests, Surveys, and Questions
- Working with Web Windows or HTML Extensions
- Publishing a Title
- Creating Web-based, Accessible Content (Section 508/WCAG)
- Lectora Layouts
- Managing Titles
- Managing your Assignments
- Managing Your Notifications
- Admin Guide
- Lectora Player Skins
- Lectora Interactions and Scenarios
- Using Tracking for Progress, Status, etc
- Working with BranchTrack
- Trouble Shooting
- Working with Audio and Video
- Working with Screen Recorder
The Training Arcade®
Rockstar Learning Platform
Can't find the answer? Ask our Customer Solutions team.
Variables are named specific to the interactions in the file.
For instance, the variable used to control the number of dates in our Playfair Textbox Interaction is: TextEnry_10013538.
In each variable, we include which interaction the variable belongs to, and which larger Course Starter file it belongs to (product number). Occasionally additional context about function may be included for more complicated interactions.
Variables that should not be edited by you start with a lowercase x.
For instance, xCheckbox2_Checked_10013538. This variable keeps track of whether or not box 2 of the Textbox Interaction has been selected—not something you're likely to want to worry about editing, and integral to the function of the template.
Don't change these values, or the file will probably break.
Exceptions are the xAPI variables. These do not include a product number and are global.
We keep them generic to make a few things clean and easy. Namely, minimizing the number of points where something could break with your xAPI statements.