Introducing GuiButton.SecondaryActivated
Key Takeaways
The GuiButton.SecondaryActivated event is now available. This routes right-clicks, long presses, and controller inputs to a single API, so you aren’t branching UI logic by device.
Hi Creators,
Today, we’re launching GuiButton.SecondaryActivated, a new event that gives you a universal, cross-platform way to handle secondary button input. It’s designed for alternative activation methods like right-click on desktop and long press on mobile, so you can support those interactions through one API instead of branching your UI logic by device.
Why This Matters
Secondary actions are a common part of modern UI patterns, but historically they’ve been awkward to implement consistently across platforms. SecondaryActivated makes that much simpler by giving GuiButton a dedicated event for those interactions.
This event currently fires on
• right-click on pointer input
• long press on touch (>1000ms)
• R3 on controller [1]
• Alt + Enter on keyboard (when using keyboard navigation)
This is especially useful for patterns like
• opening context menus
• showing secondary actions
• surfacing shortcuts
• supporting long-press interactions on touch devices
[1] SecondaryActivated fires and sinks with R3 when there is a selected GuiObject, otherwise, R3 continues to pass to systems below it
Getting Started
You can start using SecondaryActivated on any GuiButton today! For API details, see the reference documentation.
We’re excited to see what you build with it, and we’ll keep listening to feedback as creators adopt this across different UI patterns and input devices