I see here and in source code various references to non-existing examples, e.g.
/// Widget that was added by the `ContainerWidget::add_widget()` method.
///
/// ## Warning
/// You must keep your components as long as you want them to send/receive events.
/// Common practice is to store `Component`s in the `Widget` struct (see the [communication
/// example](https://github.com/antoyo/relm/blob/master/examples/communication.rs#L182-L188)).
/// The `#[widget]` attribute takes care of storing them in the struct automatically (see the
/// [communication-attribute example](https://github.com/antoyo/relm/blob/master/examples/communication-attribute.rs)).
#[must_use]
pub struct Component<WIDGET: Widget> {
stream: EventStream<WIDGET::Msg>,
widget: WIDGET::Root,
}
This is something which I need for my application (composition of components, that is), and it is really disconcerting not to have an example of how to do it, in particular, things like communication between components, in both ways (parent to child and back).
I see here and in source code various references to non-existing examples, e.g.
This is something which I need for my application (composition of components, that is), and it is really disconcerting not to have an example of how to do it, in particular, things like communication between components, in both ways (parent to child and back).