The double-click trigger has been available until Lectora v11 (i don’t know if it existed in v12) for actions on buttons, images and shapes. It has only ever worked when publishing to formats using the Lectora Viewer (CD / EXE), not when publishing to be viewed in a browser (I thought browsers don’t support double-clicks).
To create a double-click you can use Darrels code or Jennies approach by placing a transparent button over your hotspot. Add two actions to the button:
Target: This object
Target: This object
Delay: 0.5 sec
This way the real hotspot can only be clicked during the .5 seconds while the transparent button is hidden.
Other triggers only exist for certain objects:
Some triggers are only available for actions added to the page itself:
On: Keystroke (It’s not possible to press [Enter] for an image only 😉
On: Any key
On: Device rotation
On: Screen Swipe Left
On: Screen Swipe Right
Why not add “Up” and “Down”?
On: Timed Interval
Some triggers are only available for actions on certain objects:
On: Done playing
Only available for videos and audios, i.e. for “playable” objects.
On: Select / Change
Only available for form objects that can be selected, e.g. radio buttons, checkboxes, input field.
Sorry, actually the correct code is:
var username = AICC_Student_Name.getValue().split(","); Varlastname.set(username); Varfirstname.set(username);
1. Create a variable in Lectora, e.g. “allsectionsseen”
2. Create an action group on Page 1 with one action
Condition: Only if
“allsectionsseen” contains “#accordion-1” AND
“allsectionsseen” contains “#accordion-2” AND
“allsectionsseen” contains “#accordion-3”
3. Edit “Externe HTML-Objekte Code”
Under the line “var currentAttrValue = jQuery(this).attr(‘href’);”
add two lines of code:
Replace og99 with the html name of the action group created under 2.
Happy new year!
I don’t know a better way to achieve more overview than grouping those items that belong together. Usually there is no need to ungroup them again. You can edit each elements properties separately. You can move each item separately either by entering values into the position fields in the lower left corner or by holding [ALT] while moving it with the mouse.
A way to do it should be to set the variable in the way I’ve described in that other topic. Mind the action must be attached to the button. Then use the variable myAltTag for all other puposes. I’m not familiar with xAPI but it should work with
to use the variable value in the command.
If you’re using Lectoras “xAPI Statement” action, you can select the variable in the “Object” field from the dropdown or enter VAR(myAltTag)
You only need variables if you want to move the button. But as you’re using invisible buttons you could just add a second button on the left for “Close Page 1” and make the buttons show / hide each other.
If you want to move the same button, you’d need 1 variable per chapter. Give it an initial value of “0” for closed. Add an action to set the variable to “1” (if it’s 0) else set to 0. Make this the first action on the button and add conditions to all following actions depending on whether they’re are “Open” or “Close Page 1” actions.
Here’s your file. It now contains 2 ways to check whether the tasks have been done. The first uses the status indicator you’ve integrated. The second demonstrates what Jenny explained.
It also removes the Play button from the video.
Add \r to the variable:
Added on VAR(CurrentDate): VAR(Entry_0001)\r
When publishing to scorm the “Persistant data” is saved in the scorm variable “cmi.suspend_data”. The size limit of this variable depends on the scorm version. Lectora adds all variables that are “retained between sessions” to that variable with their name and value. So variables you need to retain should have the shortest possible name and value.
To reduce the amount of space needed, uncheck “retain between sessions” for all variables you don’t need to save. This can be done in the variable manager (for user-defined variables) or in the properties of the entry fields or other objects that use “Reserved variables”. Test scores are retained by default. The variables Lectora generates for a test are named as “Title_of_test_chapter_score”. It may be useful to give the test a very short name, e.g. “T1”, so the variable will be called “T1_score”, instead of a descriptive test name like “Final_Assessment_for_Chapter_1_–_Introduction_score”.
From my experience the “Move to” action is working correctly on any device, but the target coordinates are not “scaled” along with the elements on the page.
You can define a different “MoveTo” action for each device / rotation and use the variable “CurrentView” as a condition for the actions. The variable tells you whether the user uses a tablet or a phone and whether the page is viewed in portrait or landscape mode. It can have 5 different values: “Desktop”, “TabletLandscape”, “TabletPortrait”, “PhoneLandscape”, “PhonePortrait”.
So you can Move To x:100, y:200 IF CurrentView equal to “Desktop” and
another action MoveTo x:80, y:180 IF CurrentView equal to “TabletLandscape” etc.
If you want actions to only be run on a phone you can use -> IF CurrentView contains “Phone”.
IF CurrentView contains “Portrait” then actions will be run both on Phones and Tablets but only in Portrait view.
I’ve tested with some french characters in the page name and I can uncheck “Convert page names…”. It’d probably be better to get rid of them anyway, because new issues may come up with a page / filename like “précautions.html” once it’s online.
Lectora names the files in the way AssignableUnitName_ChapterName_SectionName_PageName.html. Whenever this results in two files having the same name the option to “Convert page names” can’t be unchecked. If you want to uncheck it you mustn’t have two pages with the same name, unless they are in different sections or chapters.
Change the type of your title to “AICC and SCORM for LMS”, so that you can use the scorm variables.
Identify the variable that is used to store the score: 29864_percent
Find the place where the percent score is calculated: All relevant actions are attached to the image “textBox_Intro” and executed when the image is shown.
Add another action under the calculations:
Action: Modify variable
Type: Set equal to
You’d have to update the target filename.
To receive a result you have to “Process Test / Survey”. If you have a randomized test it’s processed automatically when clicking “Next” on the last test page. If it’s not randomized you’ll have to add the “process test / survey” to the next button or any other button (That’s why Lectora adds a “Last Test Page” with a “Done” button when adding a test.) Only then the user will be directed to the pages defined under “On Completed / Passed” and “On Cancelled / Failed”.
Test_1_Score contains the test score as %, e.g. “80”. The custom progress bar uses “Range” and “Step Size”. It should be possible to use it to visualize the score if it has a range of “100” and a Step Size of “1”. The page with the progress bar must be outside the test, i.e. after processing the test.