GuiButton.Deactivated event

[sjr04 (uep)]

Currently, GuiButton.Activated exists for listening to button input from any device, however there is no Deactivated complement. Apparently, the behaviour of mousebutton1click is deprecated, so this could also be applied to MouseButton1Down? (and don’t those only fire when mice click?)

@mrow_pizza

We recommend using this event exclusively for detecting clicking/tapping/etc. on a button (MouseButton1Click’s behavior is deprecated and considered to be pretty non-idiomatic).

Use cases?

Probably just api completion, and consistency, especially with other classes such as Tool. A more specific use case would be wanting to do a certain action while a gui button is pressed, and stopping said action when released.

[mrow_pizza]

Going to share my post here as well. Sorry for the confusion! Activated fires in the same way as MouseButton1Click, not MouseButton1Down.

Button.Activated event fires when using a controller even when Active property is set to false

To be clear: the event itself is not deprecated, but the behavior where it responds to touch/gamepad events is. In the future we may phase this behavior out or provide an opt-in way to disable it. Generally, we want the mouse button events to only respond to mouse inputs; the fact that they handle touch/gamepad inputs as well is a legacy measure intended to make some games more accessible on touch devices. Activated is intended to be the cross-platform way to handle a simple “click/tap this butt…

[sjr04 (uep)]

Yeah, I knew that, but shouldn’t there be a deactivated counterpart like there is mousebutton1up/mousebutton1down ? It would be nice to have an event or something that lets us listen for all input types

[GollyGreg]

You might be able to use InputEnded events which should do exactly what you need it to do. It will fire anytime any input object stops interacting with the GuiButton, including Touch and Mouse1