Describe the bug
I have a sprite with a button state behaviour that I want to hide+a sound played if a key is pressed OR of it is touched/clicked.
However, on key pressed the sprite doesn’t want to hide?! Weirdly, the sound is played, but the sprite don’t hide?!
On mouse clicked both the the sound is played and the sprite hides.
If I remove “is clicked” it works fully with the key.
If I press s - only the sound is played, but I cant hide the sprite.
If I press on it with a mouse - both the sound is played and the sprite is hiden
When I remove the “is clicked” condition, the s key works and hides the sprite as intended.
I get it to work with “Else”. hmm not sure if the bug is that important but I am reporting 
It’s not a bug. It’s the slightly odd way that OR events work.
All of the subevents inside an OR event get evaluated even if earlier conditions are true. It triggers the actions as long as at least 1 condition is true but it means that some objects might not have any picked instances. So, the actions might not do anything.
If you press a key but don’t click a button then the key press is true but the button click is false and so it doesn’t pick the button.
You could add a pick all buttons as the first action or last condition. So, then there would always be a button in the pick list.
Your else solution is also a good solution.
Yeah… odd…I still don’t understand … But “pick all” indeed makes it works. I would never guessed this one alone.
I’ve struggled with the OR condition in the past.
Say you have 3 buttons.
If one of the following
… button1 is pressed
… button2 is pressed
… button3 is pressed
Actions
… Hide button1
… Hide button2
… Hide button3
This would only cause the pressed button(s) to be hidden because they’re the only objects with objects in their picklist.
Without any conditions, all instances are basically picked. GD uses pick lists for every object. Conditions work like filters. Objects that don’t match the condition(s) don’t get picked. Or are basically removed. You might start with 50 instances and end up with just 1 or maybe none.
Without an OR condition, the actions wouldn’t be triggered unless all 3 buttons were pressed but because of the OR, the actions get triggered as long as at least 1 condition is true.
This and other things confused me for a long time. I had to keep making small test projects to fully understand it.
