Commands not working

[jedugsem]

Hey great work,
I ported my app to android with it but I'm now noticing, that even Command::perform(async {},|_| Message::Nothing) doesnt work. It doesnt crash but it never sends Message::Nothing.
Btw i got a workspace making one codebase compile to android and desktop and even got file acces (app data only) and internet with reqwest with rusttls.
The Command thing (and subscriptions) are the only thing missing to make awesome cross applications, Thank you.
If you had other results maybe you have a hint or an idear how to debug.

[ibaryshnikov]

Hi, happy to hear about your success!

This is an integration example with no runtime, so commands and subscriptions won't work. Many of iced subscriptions (keyboard, mouse, touch) are just wrappers around winit, and we already have winit events here.

To replace a command or async subscription I can suggest using winit EventLoopProxy and user_event, it's included in the example. Something like this:

let proxy = self.proxy.clone();
std::thread::spawn(move || {
    // use some runtime to run async code if needed
    proxy.send_event(UserEvent::Nothing);
|);

iced runtime part is a bit complicated. On Android we need to use AndroidApp when creating the EventLoop:

fn android_main(android_app: AndroidApp) {
    let event_loop = EventLoop::builder()
        .with_android_app(android_app)
        .build()
        .expect("Should build event loop");

    let mut app = App::new();
    event_loop.run_app(&mut app).expect("Should run event loop");
}

And to start a runtime there's a need to call iced::run("Title", update, view). But there's no way to pass android_app into iced currently. And even if you manage to do so (I tried patching iced to pass android_app), the application just hangs up. So it requires changing some runtime logic inside iced too.

[jedugsem]

Thank you this nearly worked like i want it to ,I did
enum UserEvents { M(Message), }
and passed the message to
app_data.queue_message(message)
so i can handle all app logic in Controls.
Problem is, that after the Message got Processed there is no view call, so i have to tap for the data to appear.
Tomorow i will check if there happens a view call after the UserEvent gets processed. Do you have an idear how to add that call?

[ibaryshnikov]

The workflow looks like this:

state.queue_event() or state.queue_message()
state.update()
window.request_redraw()

Did you call all of these?

[jedugsem]

Thank you, i was missing both last methods and now it works. I now have replacement for every feature used by my libcosmic app and all helper functions work. Now I'll port the ui. And probably publish it soon.

[dcampbell24]

Any progress on getting the runtime working? It seems that we need a minor change just to build now: iced-rs/iced#3099 .

[ibaryshnikov]

@dcampbell24 hey, thanks for reaching out! There's no such a goal though, I'm happy with user events and EventLoopProxy

[dcampbell24]

As a side note it seems to work (at least run) with https://f-droid.org/en/packages/com.termux/ .