writing to a TextEditor from another thread

[permezel]

I have a simple app and I want to use the text editor to display continuously updated information, as if on a terminal.
I am trying to use the TextEditor to do so, plus using RwSignal to hold the new text.

fn app_view() -> impl IntoView {
    let text_updates: RwSignal<Option<String>> = create_rw_signal(None);

    let ed = text_editor("")
        .styling(SimpleStyling::new())
        .style(|s| s.size_full())
        .editor_style(default_dark_color);

    let shared_ed = ed.shared_editor();
    let view = stack((ed,))
        .style(|s| s.size_full().flex_col().items_center().justify_center());

    let text_updates_clone = text_updates.clone();
    
    // Background thread to modify text
    thread::spawn(move || {
        loop {
            thread::sleep(Duration::from_secs(2));
            text_updates_clone.set(Some("Hi there!".to_string()));

            thread::sleep(Duration::from_millis(10_000));
            text_updates_clone.set(Some(" ".to_string()));
        }
    });

    create_effect(move |_| {
        if let Some(new_text) = text_updates.get() {
            dbg!(&new_text); // Debugging to confirm effect runs
            let mut doc = shared_ed.doc();
            let text = doc.text();
            doc.edit_single(Selection::caret(text.len()), &new_text, EditType::InsertChars);
        }
    });

    let id = view.id();
    view.on_key_up(
        Key::Named(NamedKey::F11),
        |m| m.is_empty(),
        move |_| id.inspect(),
    )

The created effect never fires. How do I tie the signal to the view?
I have tried alternate schemes where I pass the shared_ed to some other thread (the preferred approach) that does not pass the compiler.
How am I supposed to write to my Document?

[jrmoulton]

https://docs.rs/floem/latest/floem/ext_event/fn.create_signal_from_channel.html
https://docs.rs/floem/latest/floem/ext_event/fn.update_signal_from_channel.html

With feature flags you can also enable channels from tokio channels or from future streams.

You need to write to a channel on another thread and have a signal receive it on the main thread.

Signals shouldn't be able to be sent to other threads either as they are tied to the thread on which they are created so that code shouldn't have compiled either. Signals used to be !Send but that was removed at some point. I've just pushed a PR that makes signals !Send again.