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.
Agreed, @shanwoman & Sergey. Right now, in almost every Lectora course we build, I have to manually account for a "visited" state using some combination of show/hide, changeContents, or some other Lectora sorcery.
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
Thanks, Adam. Yes, I'd love to hear about your workarounds. What I've been doing is using status indicators and creating a color and grayed out version of each image in Photoshop. But this means I can't have a hover state. Also, if you use a shadow or any kind of effect on a status indicator image, it often means you won't see a "hand cursor" when hovering over the image. Trivantis has identified this as a bug. What types of workarounds have you had success with?
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. :-)
How about this workaround:
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 used a visited variable and then add to that each time button is clicked.
I have created my own Button group for each state
All buttons are groups
___[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
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.
I'm looking for a 'down' state for buttons - one that remains after I move the mouse away. The same as a 'visited' state in other authoring tools.
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?
So many limitations in this product that are self-imposed.
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.
I agree. We just change tool to lectora and surprised that there are no visited state or clicked state that stays as long as you dont mark another one. I am used to do a lot of work arounds but now when we should follow WCAG and accessibility we want to limited the risk to make things that not work for everyone.
Prior to 2010 it was possible to use :visited to access user browser history and even enough information to guess at a persons identity, however browsers now limit the information that can be gleaned from nefariously using CSS styles (with JS and PHP) by limiting what can be styled and reported back to a server. Guess what, everything you need to have visited styled links/buttons (color, background-color, outline-color, border-color and more) has been available for ten years plus now.
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.
Just nudging this back into the light...it appears this feature is now available on the desktop version, but still pending for Lectora Online. I hear it is on the horizon, but taking a moment to advocate for the feature in the online platform sooner rather than later, please :-)
- 35.9K All Categories
- 109 ✫ Announcements
- 33.1K Lectora®
- 31.1K Lectora Discussions
- 29K Lectora Desktop
- 2K Lectora Online
- 2K Lectora Feature Requests
- 71 Lectora User Groups
- 36 Lectora Accessibility User Group (LAUG)
- 25 ELB Learning Content
- 25 ELB Learning Content Discussions
- 329 CenarioVR®
- 196 CenarioVR Discussions
- 133 CenarioVR Feature Requests
- 42 Rockstar Learning Platform®
- 39 Rockstar Learning Platform Discussions
- 108 CourseMill®
- 108 CourseMill Discussions
- 47 ReviewLink®
- 47 ReviewLink Discussions
- 7 The Training Arcade®
- 7 The Training Arcade Discussions
- 936 All Things eLearning
- 37 eLearning Development
- 546 Learning Management System (LMS) Integration
- 333 Web Accessibility
- 1.2K ♪ The Green Room
- 9 Additional Learning Products