> For the complete documentation index, see [llms.txt](https://docs.flatredball.com/gum/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flatredball.com/gum/code/gum-code-reference/interactivegue.md). # InteractiveGue ### Introduction The InteractiveGue class provides a base class for custom runtimes which need to interact with the cursor. All visuals for Gum Forms use Visuals which inherit from InteractiveGue, such as ContainerRuntime. InteractiveGue ultimately provides more events than most controls need for normal behavior. For example, Button does not include a Dragging event, but InteractiveGue (ultimately the Visual for all Buttons) does. Therefore, additional behavior can be added to Forms by subscribing to underlying events on their Visual. ## InteractiveGue Events The following events are available on InteractiveGue * Click * Push * LosePush * DoubleClick * RightClick * RollOn * RollOff * RollOver * HoverOver * Dragging * RemovedAsPushed * MouseWheelScroll For more information on visual events, see the [Visual Events](/gum/code/events-and-interactivity/visual-events.md) page. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.flatredball.com/gum/code/gum-code-reference/interactivegue.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.