May 17, 2015 at 4:04 pm #283272
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.This post has received 8 votes up.May 18, 2015 at 9:00 am #286933
Sergey SnegirevMember337 pts@ssneg
Sounds like a nice idea.May 22, 2015 at 2:19 pm #294499
Adam LeiblerMember12 pts@AdamLeibler
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
eLearning BrothersThis post has received 1 vote up.June 5, 2015 at 5:36 pm #295933
Trivantis SupportModerator18 pts@Support
I’ll submit this as a feature request 🙂This post has received 1 vote up.June 30, 2015 at 10:35 pm #297098
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. 🙂October 21, 2015 at 9:16 am #301125
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.October 27, 2015 at 8:28 am #301279
Adam – please contact me to discuss your work arounds. david.mark@Maryland.govNovember 2, 2015 at 11:03 pm #301574
Trav OwersMember1 pt@towers9815
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.
- This reply was modified 1 year, 8 months ago by Trav Owers.
Attachments:September 27, 2016 at 3:45 pm #328163
I’m back to using Lectora for a new project after being away for a year. I just downloaded 16.2 and can it be that this still has not been fixed by the fine folks at Trivantis? No visited state for buttons? Or am I missing something?This post has received 1 vote up.September 27, 2016 at 4:23 pm #328177
Certainly surprising that this hasn’t been included by default considering the major competitors in this space offer it.October 14, 2016 at 11:14 am #329420
Am just wondering about this myself, could anyone from Trivantis provide details?
Thank you!October 18, 2016 at 8:44 am #329822
Darrel SomozaMember145 pts@Klaatu
Go to this POST for a simple solution that provides zero graphic (no weight) buttons that can have a visited style. Very easy to do.February 24, 2017 at 12:39 am #347250
amanda hetheringtonMember3 pts@ahetherington9113
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?
AmandaMarch 1, 2017 at 11:44 pm #347979
Peter SorensonMember1 pt@peterLEXsorenson
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.
You must be logged in to reply to this topic.