Name Description Size Coverage
button.rs 709 -
checkbox.rs 668 -
hbox.rs 1089 -
label.rs 589 -
mod.rs The UI model. Model elements should generally be declared as types with all fields `pub` (to be accessed by UI implementations), though accessor methods are acceptable if needed. An `ElementBuilder<TYPE>` impl should be provided to create methods that will be used in the [`ui!`] macro. The model types are accessible when being _consumed_ by a UI implementation, whereas the `ElementBuilder` types are accessible when the model is being _created_. All elements should be listed in the `element_types!` macro in this file (note that [`Window`], while an element, isn't listed here as it cannot be a child element). This populates the `ElementType` enum and generates `From<Element>` for `ElementType`, and `TryFrom<ElementType>` for the element (as well as reference `TryFrom`). The model is written to accommodate layout and text direction differences (e.g. for RTL languages), and UI implementations are expected to account for this correctly. 10653 -
progress.rs 602 -
scroll.rs 513 -
textbox.rs 784 -
vbox.rs 614 -
window.rs 1477 -