osui-rs/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fixed broken links

Browse Source
This commit is contained in:
selimaj-dev
2025-08-10 14:28:53 -05:00
parent b4891d4795
commit 05156a84ba
16 changed files with 60 additions and 60 deletions
Download Patch File Download Diff File Expand all files Collapse all files
versioned_docs/version-0.1.0/01-guides/handling_input.md
+1 -1
View File
@@ -128,7 +128,7 @@ rsx! {
Beyond `crossterm` events, you can define and dispatch your own custom event types using the `event!` macro. This is useful for communication between different parts of your application or custom extensions.
See the [Advanced: Custom Events](/docs/advanced/custom_events) guide for details.
See the [Advanced: Custom Events](/docs/0.1.0/advanced/custom_events) guide for details.
## Summary
versioned_docs/version-0.1.0/01-guides/using_extensions.md
+4 -4
View File
@@ -105,10 +105,10 @@ Once registered, the `Screen` will call the appropriate lifecycle methods of you
OSUI comes with several useful built-in extensions:
* [`InputExtension`](/docs/reference/extensions_api#inputextension): Handles keyboard input and dispatches `crossterm::event::Event`s. **Crucial for interactive applications.**
* [`TickExtension`](/docs/reference/extensions_api#tickextension): Dispatches `TickEvent`s at a specified rate, useful for animations or periodic updates.
* [`VelocityExtension`](/docs/reference/extensions_api#velocityextension): Automatically updates the `Transform` of widgets that have a `Velocity` component, causing them to move.
* [`IdExtension`](/docs/reference/extensions_api#idextension): Provides a way to retrieve specific widgets by a unique `Id` component. (Note: The current `IdExtension` implementation only *stores* a screen reference but doesn't actively do anything unless you manually call its `get_element` method.)
* [`InputExtension`](/docs/0.1.0/reference/extensions_api#inputextension): Handles keyboard input and dispatches `crossterm::event::Event`s. **Crucial for interactive applications.**
* [`TickExtension`](/docs/0.1.0/reference/extensions_api#tickextension): Dispatches `TickEvent`s at a specified rate, useful for animations or periodic updates.
* [`VelocityExtension`](/docs/0.1.0/reference/extensions_api#velocityextension): Automatically updates the `Transform` of widgets that have a `Velocity` component, causing them to move.
* [`IdExtension`](/docs/0.1.0/reference/extensions_api#idextension): Provides a way to retrieve specific widgets by a unique `Id` component. (Note: The current `IdExtension` implementation only *stores* a screen reference but doesn't actively do anything unless you manually call its `get_element` method.)
You use these built-in extensions by simply calling `screen.extension(...)` with an instance of them, just like `MyLoggerExtension`.