Selected / Hover state - what about selected hover??

Good effort Walt, that's a load of triggers to go with the custom state. Your example shows what most users want the buttons to do. But for lots of menu pages with multiple buttons linking to other pages, its a lengthy workaround and tricky to get a team across without someone mucking it up when editing (e.g. making button adjustments and additions on the fly). For a long course, its a lot of tinkering with buttons. I have tinkered with custom triggers and states to workaround this matter also, and find that method to be quite cumbersome and involved.

This matter should really be fixed in the Storyline 360 authoring program, and set different to how it is at present. This issue was flagged to Articulate here 7 years ago.

It was also flagged here 5 years ago - https://community.articulate.com/discussions/building-better-courses/tutorial-getting-the-hover-state-to-behave-itself

The above discussion contains an alternate workaround which like the workarounds discussed here should not be necessary. Its also somewhat inelegant and messy (e.g. after I cut and paste a button within a state (just to shift what layer it appears on in relation to other states), the button often changes size which then requires adjusting to match other states. My usage of that method over some time now confirms that the order in which users cut and paste states (or add new states) influences what state appears above others. This finding is not a product feature but a quirk not documented by the vendor, presumably not intended, but used by customers to get buggy buttons to become publishable for elearning projects.

This issue could be resolved by Articulate via:

1. a change to default configuration in Storyline so that Hover states do not appear above Selected or Visited States after being clicked - until after user moves cursor away from the object then moves back over button. This solution would not require users to make custom workarounds to a commercial authoring tool. Or;

2. add options to the 'Hover' state. Such as a tickbox for 'appear above Selected state after being clicked' and 'appear above Visited state after being clicked'. Storyline sets that option as unticked by default for buttons users create. Which means the problem is solved for most users. This way, if users have a desire to have the Hover state show above the Selected or Visited state right after clicking it (for a scenario I have not required yet) the option is there.

Fellow customers, the link to log bug fix issues is below. 

https://articulate.com/support/contact/feature-request

I've logged a request including example files and documents.