Visited State for Buttons

I can't believe Lectora 12 doesn't have a visited state for buttons. Am I wrong? Storyline has this and clients now expect a gray button after it has been clicked. The disable state doesn't fit this need as the learner cannot go back and revisit the link if the button is disabled.
0
Categories
- 34 ✫ Announcements
- 6 ✪ Contests
- 34K eLearning Brothers® Products
- 1 AssetLibrary™
- AssetLibrary Discussions
- 1 AssetLibrary Feature Requests
- 38 CenarioVR®
- 103 CenarioVR Discussions
- 55 CenarioVR Feature Requests
- 1 CourseMill®
- 101 CourseMill Discussions
- 1 KnowledgeLink®
- KnowledgeLink Discussions
- 1 KnowledgeLink Feature Requests
- 66 Lectora®
- 1.1K Lectora Discussions
- 1.9K Lectora Feature Requests
- 53 Lectora User Groups
- 4 Off-the-Shelf Course Library
- 3 Off-the-Shelf Course Library Discussions
- 1 Off-the-Shelf Course Library Feature Requests
- ReviewLink®
- 21 ReviewLink Discussions
- 12 ReviewLink Suggestions
- 1 The Training Arcade®
- 1 The Training Arcade Discussions
- The Training Arcade Feature Requests
- 7 Additional Learning Products
- 2 Adobe®
- 2 Articulate®
- 1 Camtasia®
- Docebo®
- 1 iSpring®
- 1 Microsoft® PowerPoint®
- 288 All Things eLearning
- 3 Course Development Showcase
- 1 eLearning Brothers® Downloads
- 1 Compliance Training
- 4 eLearning Development
- eLearning Game Design
- 7 Instructional Design
- 264 Learning Management System (LMS) Integration
- 2 Mobile Learning
- 2 Visual Design
- 317 Web Accessibility
- 579 ♪ The Green Room
- 2 ♡ Community Feedback
Comments
It'd be nice to have this as a fifth button state to avoid that extra work in the pipeline.
In the meantime, I'd be happy to share some of my workarounds with you, @shanwoman, if you need 'em. :-)
Adam Leibler, LCA
Senior eLearning Developer
eLearning Brothers
By the way, sorry for the long delay in replying. I had forgotten to check the box to be notified of replies to my post. Just now happened upon your reply. :-)
Add a button (it would be a checkmark) whose initial state would be hidden. After a button is clicked and the state changed to the clicked state, the hidden button would appear and be placed atop of the original button showing the user that this has been completed/viewed.
Storyline does this same thing, but a bit easier.
I have created my own Button group for each state
All buttons are groups
[button Example]
___[Image Blue] - Normal State (Background of the button)
___[Image Gold] - Selected State (For when its active)
___[Image Grey] - Disable State
___[Clear with Tick] - Visited State
______Action: On Show Hide IF...(see below)
___[Text Box] - Button Text
___[Transparent Button] Normal: Empty 100 Opacity (Clear)
_______________Down: Colour at 70 Opacity
_______________Over: Colour at 40 Opacity
______Action: On_MClk_Goto...
______Action: On_MClk_Goto_ModVar_IF
I have created a variable that will hold each visit. I called it ButtonVisited.
So on each button I have Modify Var Action that added the <<CurrentPageName>>+"A" to the variable.
Visited State image has on Show IF ButtonVisited does not contain <<CurrentPageName>>+"A". Where A is button on this page.
If you have more than one button it would be B and then C, (Sure you can see the pattern)
Note: I always keep my page names to just numbers as you might run out of space for SCORM 1.2.
Also you might ask why an image. Well each image is only 1 pixel by 1 pixel. This means that I can use the same image for button of any size!
Well thats one way to do it till its a standard feature.
Thank you!
I'm using Lectora 17.1 and still only have 4 button states, including 'down' but this only appears while you hold the mouse click on the button, so I'm assuming 'visited' still requires a workaround?
Cheers
Amanda
<http://www.apixel.com/atelier/page05t.htm>
which mimics Captivate's smart shape object, allowing you to create buttons with "visited" states in Lectora. It's based on JavaScript but it doesn't look difficult to use.
Why not allow the user to create their own states in addition to the native core four?
I need a "clicked/selected" state - where the button can now include a checkmark to signify the button has been selected. No opportunity to make my own.
But the button still resources an image - so - with a little bit of javascript you can overcome the #Lectoralimitation.
Mimic Captivate's smart object
Again, as great as it is this program needs serious retooling as it is getting long in the tooth. Why isn't css grid being used? Why not use CSS buttons without the weight of graphics? Why not output industry web standard html5? Why are actions so limited? Take a look at the actions that Toolbook provided back in 2012 before it was bought by Skillsoft to be killed; to this day it still blows Inspire's action capability out of the water and that's natively without adding external JavaScript. Just look at what what you could easily manipulate.
eLearning Brothers has a fantastic opportunity to do what StoneCalibre didn't, listen to your users and add the things that have been requested for years, fix the issues that have plagued users for years and finally, use and output standard HTML5.