From 10102017a3a76b5b6aa81c6fbabdc2f64e198376 Mon Sep 17 00:00:00 2001 From: Leo dev Date: Sun, 3 Aug 2025 13:10:03 -0500 Subject: [PATCH] fix broken links --- versioned_docs/version-0.1.0/advanced/contributing.md | 3 --- versioned_docs/version-0.1.0/concepts/rendering_pipeline.md | 2 +- versioned_docs/version-0.1.0/reference/widget_api.md | 2 +- 3 files changed, 2 insertions(+), 5 deletions(-) diff --git a/versioned_docs/version-0.1.0/advanced/contributing.md b/versioned_docs/version-0.1.0/advanced/contributing.md index 37ea00a..1f65f35 100644 --- a/versioned_docs/version-0.1.0/advanced/contributing.md +++ b/versioned_docs/version-0.1.0/advanced/contributing.md @@ -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. Thank you for considering contributing to OSUI! Your efforts help make this project better for everyone. - -[**Return to Overview**](../intro/overview.md) - diff --git a/versioned_docs/version-0.1.0/concepts/rendering_pipeline.md b/versioned_docs/version-0.1.0/concepts/rendering_pipeline.md index ce174ff..dbdaf95 100644 --- a/versioned_docs/version-0.1.0/concepts/rendering_pipeline.md +++ b/versioned_docs/version-0.1.0/concepts/rendering_pipeline.md @@ -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. * `draw_child(&mut self, element: &Arc)`: 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` diff --git a/versioned_docs/version-0.1.0/reference/widget_api.md b/versioned_docs/version-0.1.0/reference/widget_api.md index 22a0404..94aa3af 100644 --- a/versioned_docs/version-0.1.0/reference/widget_api.md +++ b/versioned_docs/version-0.1.0/reference/widget_api.md @@ -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. * `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`: (Described in [Handling Input](../guides/handling_input.md) and [Extensions API](../reference/extensions_api.md)) Enables widgets to subscribe to specific event types. +* `Handler`: (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