dbus: Use ThreadPool instead of zbus blocking API
The `zbus` blocking API just wraps the async API with `block_on`, so we may as well use our own executor.
This commit is contained in:
parent
8455869439
commit
55401b1e53
5 changed files with 26 additions and 29 deletions
1
Cargo.lock
generated
1
Cargo.lock
generated
|
|
@ -834,6 +834,7 @@ dependencies = [
|
|||
"egui",
|
||||
"egui_plot",
|
||||
"futures-executor",
|
||||
"futures-util",
|
||||
"i18n-embed",
|
||||
"i18n-embed-fl",
|
||||
"iced_tiny_skia",
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue