Else function in triggers

I have personally found some wonky behavior over the years when trying to run triggers based on images and buttons changing states. I'm not ruling out that the problem existed between the keyboard and chair.

An else condition can only be added if you incorporate a conditional, and that may not fit your exact situation. The easiest most direct solution is for each layer to have the property of hiding other slide layers:

A downside to the above method is that it will hide ALL other slide layers. I often do not want that as I like to use other layers for different popups and chunks of information. If the only layers are the button ones, you'll likely be fine, but if you have other layers, the below method may work better. 

I've had much greater success by having buttons update a single number variable and then cascading changes based on that variable, like showing and hiding layers based on the value of the variable.

Each button changes the variable:

Then when the variable changes, show or hide the appropriate layer:

This also enables my favorite streamliner: making it much simpler to return unselected buttons to their default Normal state:

Those triggers make it very easy to implement the accessibility improvement of showing the learner which button is currently selected. It's not always obvious which one they're on, and I've done the trigger dance before of changing button 1 back to normal when another is in the selected state, and the above just seems easier and more elegant to me. and scales up really well I think to a large number of buttons and layers.

You can see the idea in action here: https://360.articulate.com/review/content/b420ac79-1fc7-4b33-a978-08d29472bee7/review