Frequently Asked Questions

When Will the Book Be Finished?

Soon™. Open source is a gift; so whenever I feel like it.

You split your application into multiple screens, and then use simple composition.

You can use Task::run to generate messages from an asynchronous Stream.

Alternatively, if you control the creation of the channel; you can use Subscription::run.

Not very well yet!

You may be able to render some scripts using Text::shaping with Shaping::Advanced, but text editing for these scripts is not yet supported; and neither are Input Method Editors.

These features are in the ROADMAP, however!

After every batch of messages and update calls. But this is an implementation detail; and should never rely on this.

Try to treat these functions as declarative, stateless functions.

Yes! iced currently redraws after every runtime event; including tiny mouse movements.

There are plans to redraw less frequently by detecting widget state changes, but performance has not been a priority so far.

The renderers do perform quite a lot of caching; so redrawing is quite cheap. As a result, this is rarely an issue for most use cases!

You are probably using Task to execute a Future that needs the tokio executor:

there is no reactor running, must be called from the context of a Tokio 1.x runtime

You should be able to fix this issue by enabling the tokio feature flag in the iced crate:

iced = { version = "0.13", features = ["tokio"] }