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

fix broken links

Browse Source
This commit is contained in:
selimaj-dev
2025-08-03 13:10:03 -05:00
parent d35cc6408d
commit 10102017a3
3 changed files with 2 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
versioned_docs/version-0.1.0/advanced/contributing.md
-3
View File
@@ -59,6 +59,3 @@ We welcome contributions to OSUI! Whether it's reporting bugs, suggesting featur
* **Formatting**: Use `cargo fmt` to automatically format your code according to Rust's standard style. * **Formatting**: Use `cargo fmt` to automatically format your code according to Rust's standard style.
Thank you for considering contributing to OSUI! Your efforts help make this project better for everyone. Thank you for considering contributing to OSUI! Your efforts help make this project better for everyone.
[**Return to Overview**](../intro/overview.md)
versioned_docs/version-0.1.0/concepts/rendering_pipeline.md
+1 -1
View File
@@ -49,7 +49,7 @@ The actual drawable logic. Each `Element` implementation defines how it appears.
* `after_render(&mut self, scope: &mut RenderScope)`: For containers, this is where children are processed and recursively rendered. It's also where the element might determine its final `Dimension::Content` size based on children. * `after_render(&mut self, scope: &mut RenderScope)`: For containers, this is where children are processed and recursively rendered. It's also where the element might determine its final `Dimension::Content` size based on children.
* `draw_child(&mut self, element: &Arc<Widget>)`: Called by `rsx!` to establish parent-child relationships. Children processed by a parent are marked `NoRenderRoot` to prevent the `Screen` from rendering them independently. * `draw_child(&mut self, element: &Arc<Widget>)`: Called by `rsx!` to establish parent-child relationships. Children processed by a parent are marked `NoRenderRoot` to prevent the `Screen` from rendering them independently.
(See [Reference: Widget API - Element Trait](../reference/widget_api.md#element-trait) and [Guides: Custom Elements](../guides/custom_elements.md) for more details) (See [Reference: Widget API - Element Trait](/reference/widget_api#element-trait) and [Guides: Custom Elements](/docs/guides/custom_elements) for more details)
### 4. `RenderScope` ### 4. `RenderScope`
versioned_docs/version-0.1.0/reference/widget_api.md
+1 -1
View File
@@ -141,7 +141,7 @@ OSUI uses a few internal components to control rendering behavior:
* `NoRender`: If a widget has this component, the `Screen`'s main rendering loop will skip rendering it directly. This is typically used for widgets that are managed and rendered by their parent `Element::after_render` method. * `NoRender`: If a widget has this component, the `Screen`'s main rendering loop will skip rendering it directly. This is typically used for widgets that are managed and rendered by their parent `Element::after_render` method.
* `NoRenderRoot`: Similar to `NoRender`, but specifically signals that the widget is a child being managed by a parent element, preventing the `Screen` from considering it a top-level root widget for direct rendering. * `NoRenderRoot`: Similar to `NoRender`, but specifically signals that the widget is a child being managed by a parent element, preventing the `Screen` from considering it a top-level root widget for direct rendering.
* `Handler<E>`: (Described in [Handling Input](../guides/handling_input.md) and [Extensions API](../reference/extensions_api.md)) Enables widgets to subscribe to specific event types. * `Handler<E>`: (Described in [Handling Input](/docs/guides/handling_input.md) and [Extensions API](../reference/extensions_api.md)) Enables widgets to subscribe to specific event types.
## Usage Patterns ## Usage Patterns