dnrops
/
xilem
mirror of https://github.com/linebender/xilem
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix doc links by either correcting the item name, or making these public (#499) 

I don't think anything speaks against making the items public in
masonry?
This commit is contained in:
Philipp Mildenberger 2024-08-09 18:11:02 +02:00 committed by GitHub
parent 2dc7b80153
commit 8ecdd876dc
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
4 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
masonry/src/lib.rs
View File

@ -131,7 +131,7 @@ pub use action::Action;
pub use box_constraints::BoxConstraints; pub use box_constraints::BoxConstraints;
pub use contexts::{ pub use contexts::{
AccessCtx, EventCtx, IsContext, LayoutCtx, LifeCycleCtx, PaintCtx, RawWrapper, RawWrapperMut, AccessCtx, EventCtx, IsContext, LayoutCtx, LifeCycleCtx, PaintCtx, RawWrapper, RawWrapperMut,
WidgetCtx, WidgetCtx, WorkerCtx,
}; };
pub use event::{ pub use event::{
AccessEvent, InternalLifeCycle, LifeCycle, PointerButton, PointerEvent, PointerState, AccessEvent, InternalLifeCycle, LifeCycle, PointerButton, PointerEvent, PointerState,

2
masonry/src/testing/mod.rs
View File

@ -14,7 +14,7 @@ mod screenshots;
#[cfg(not(tarpaulin_include))] #[cfg(not(tarpaulin_include))]
mod snapshot_utils; mod snapshot_utils;
pub use harness::{TestHarness, HARNESS_DEFAULT_SIZE}; pub use harness::{TestHarness, HARNESS_DEFAULT_BACKGROUND_COLOR, HARNESS_DEFAULT_SIZE};
pub use helper_widgets::{ModularWidget, Record, Recorder, Recording, ReplaceChild, TestWidgetExt}; pub use helper_widgets::{ModularWidget, Record, Recorder, Recording, ReplaceChild, TestWidgetExt};
use crate::WidgetId; use crate::WidgetId;

6
xilem_core/src/deferred.rs
View File

@ -10,7 +10,7 @@ use crate::{DynMessage, Message, NoElement, View, ViewId, ViewPathTracker};
/// A `Context` for a [`View`](crate::View) implementation which supports /// A `Context` for a [`View`](crate::View) implementation which supports
/// asynchronous message reporting. /// asynchronous message reporting.
pub trait AsyncCtx<Message = DynMessage>: ViewPathTracker { pub trait AsyncCtx<Message = DynMessage>: ViewPathTracker {
/// Get a [`Proxy`] for this context. /// Get a [`RawProxy`] for this context.
// TODO: Maybe store the current path within this Proxy? // TODO: Maybe store the current path within this Proxy?
fn proxy(&mut self) -> Arc<dyn RawProxy<Message>>; fn proxy(&mut self) -> Arc<dyn RawProxy<Message>>;
} }
@ -28,7 +28,7 @@ pub trait AsyncCtx<Message = DynMessage>: ViewPathTracker {
/// ///
/// ## Lifetimes /// ## Lifetimes
/// ///
/// It is valid for a [`Proxy`] to outlive the [`View`](crate::View) it is associated with. /// It is valid for a [`RawProxy`] to outlive the [`View`](crate::View) it is associated with.
pub trait RawProxy<Message = DynMessage>: Send + Sync + 'static { pub trait RawProxy<Message = DynMessage>: Send + Sync + 'static {
/// Send a `message` to the view at `path` in this driver. /// Send a `message` to the view at `path` in this driver.
/// ///
@ -87,7 +87,7 @@ where
{ {
} }
/// The potential error conditions from a [`Proxy`] sending a message /// The potential error conditions from a [`RawProxy`] sending a message
#[derive(Debug)] #[derive(Debug)]
pub enum ProxyError { pub enum ProxyError {
/// The underlying driver (such as an event loop) is no longer running. /// The underlying driver (such as an event loop) is no longer running.

2
xilem_web/src/concurrent/memoized_await.rs
View File

@ -58,7 +58,7 @@ where
/// Await a future returned by `init_future` invoked with the argument `data`, `callback` is called with the output of the resolved future. `init_future` will be invoked again, when `data` changes. /// Await a future returned by `init_future` invoked with the argument `data`, `callback` is called with the output of the resolved future. `init_future` will be invoked again, when `data` changes.
/// ///
/// The update behavior can be controlled, by [`debounce`](`MemoizedAwait::debounce`) and [`reset_debounce_on_update`](`MemoizedAwait::reset_debounce_on_update`) /// The update behavior can be controlled, by [`debounce_ms`](`MemoizedAwait::debounce_ms`) and [`reset_debounce_on_update`](`MemoizedAwait::reset_debounce_on_update`)
/// ///
/// # Examples /// # Examples
/// ///