Forum Discussion
The use of buttons (particularly the Storyline default buttons) and states is an example of code due for an overhaul. On the Articulate forums, I see many issues regarding the quirks new users experience when using buttons - e.g. hover appearing above selected state (logged 2014).
In a Jan 2023 tip from longtime staffer on how to combine hover and selected states the Bibby cut and paste button states technique (logged 2017) is demonstrated as a workaround to override default button behaviour, along with other ideas that users tend to figure out themselves over time (such as changing the appearance of hover to make it more subtle when it appears above other states).
Tidying up the default button behaviours to be more consistent and straightforward to program would lessen the random outcomes that new users complain about. I have several workarounds to the button issues and use whatever is required at the time, which often involves testing and editing until it works; if it simply worked consistently every time without looking for workarounds that would be an improvement. Users often create their own *.png buttons externally (in an image editing app such as Adobe Illustrator) then import, which I often do also for working around the look of default hovers without having to use extra triggers. I often do this because others may end up having to deal with these later when making future updates to my courses.
When I have logged tickets and provided files, the initial response has often felt like the representative responding is providing content from a how-to-guide rather than responding directly to the issue encountered. The improvement suggestions I have logged with Articulate result only in a vague and non-commital autoreply email in my inbox. Some fellow users I know have given up logging issues with Articulate, other than the occasional support ticket if they require assistance on workarounds that are not well documented on the forums already and have a tight deadline to meet.
- SamHill2 years agoSuper Hero
Thanks for your comments on buttons Reuben. I couldn't agree more.
This is the kind of behaviour that we learn to live with (for the worse) and we are reminded frequently how ridiculous it is when explaining it to new developers or clients.
Another major bug bear of mine is that every element you add to stage has ALT text by default. Sure text boxes and jpgs, PNG's etc, but shapes drawn in Storyline and and icons imported through to stock library are sometime composed of grouped shapes where each element has a junk ALT text defined. This is extra unnecessary work as we must clear this stuff up for screen reader users.