0.5->0.6 migration advice?

[mock1328]

For study purpose, I tried upgrading the package that I use, regreet, onto newer gtk-rs/relm4 version. However, everything above 0.5 fails to compile, this view! components, to be specific. It can't find the template_child elements, even though vscode manages to find them correctly into the templates.rs file, and these have correct #[name] attribute set up:

(example of error for user_toggle

cannot find value `user_toggle` in this scope
not found in this scope

But I guess this was fixed in 0.6.2, so when upgrading to 0.7 or higher versions, some of compilation errors go away, but some related to connect_clicked are not:

e.g. for this code:

                    connect_activate[
                        sender, usernames_box, username_entry, sessions_box, session_entry
                    ] => move |this| {
                        sender.input(Self::Input::Login {
                            input: this.text().to_string(),
                            info: UserSessInfo::extract(
                                &usernames_box, &username_entry, &sessions_box, &session_entry
                            ),
                        })
                    }

I have an error:

cannot find value `usernames_box` in this scope
component.rs(229, 34): the binding `usernames_box` is available in a different scope in the same function

Thourgh trial-and-error I've managed to fix (?) it by making these references with &:

                    connect_activate[
                        sender, &usernames_box, &username_entry, &sessions_box, &session_entry
                    ] => move |this| {

However, now it errors on move statement:

used binding `usernames_box` isn't initialized
`usernames_box` used here but it isn't initialized
...

I've asked the same question in gtk-rs repo, and they say it's probably related to my relm4 usage, rather than gtk-rs breakage. The migration guide, changelog, changes in examples between 0.5.1 and 0.6.0 tags are not giving useful information, so I'm a bit stuck...

[AaronErhardt]

I think in 0.5 template children accidentally "tainted" the scope of the entire view macro (because they were globally available, which made it impossible to refer to the children when using the same template twice). Now you should be able to access it like you would do in regular Rust: parent.child_name.

In you case, that would mean something like this:

                    connect_activate[
                        sender, usernames_box = ui.usernames_box.clone(), username_entry, sessions_box, session_entry
                    ]

[mock1328]

Thanks for advice! Works like a charm :)