Consistency Issues with Button States
May 29, 2014
I am working on a rather large course with lots of buttons controlling media files, interaction play and feedback, etc.). In testing the course (myself and others) I am finding that the default button states are not very consistent.
A couple of questions.
Is there a resource that defines the default button states? (or are there any).
Meaning, what constitutes a default visited state ( mouse clicks once and loses focus, timeline ends, media completes, etc.) ?
Or do the active, visited and disabled states all have to be defined by triggers? If so, can are there some examples? I find even when I add a trigger it is not always producing the right result.
Has anyone found inconsistency created by using the format painter and/or copy and pasting buttons from one slide to the other?
Thanks for any light you can shed on this matter.
~Rebecca
1 Reply
Hi Rebecca,
I have noticed some weird behaviors when it comes to the default states. I usually only stick to Norma, Hover, and Selected states. If I need to use a "visited" state, I usually create my own state and called it "completed". You also have to keep in mind other layer and slide triggers that may be effecting the buttons. If you have the slide or layers to reset to initial state upon resuming, this may set the buttons back to the original state.
This discussion is closed. You can start a new discussion or contact Articulate Support.