-
-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider removing channels from glib #1213
Comments
sdroege
added a commit
to sdroege/gtk-rs-core
that referenced
this issue
Oct 30, 2023
Async code generally allows for more flexible message handling than the callback based MainContext channel. Fixes gtk-rs#1213
sdroege
added a commit
to sdroege/gtk-rs-core
that referenced
this issue
Oct 30, 2023
Async code generally allows for more flexible message handling than the callback based MainContext channel. Fixes gtk-rs#1213
See #1216 |
bilelmoussaoui
pushed a commit
that referenced
this issue
Oct 30, 2023
Async code generally allows for more flexible message handling than the callback based MainContext channel. Fixes #1213
Splendid move! Could you consider using Rust's deprecated attribute next time, let's say, for 2 releases? |
It was deprecated during the release cycle of 0.18.x. |
First release without the API was on Sunday, so that gives a bit more than 2 months. |
robmoss
added a commit
to robmoss/rusty_train
that referenced
this issue
Feb 19, 2024
Channels were removed from glib 0.19, and so we use the async-channel crate instead (see gtk-rs/gtk-rs-core#1213). It took some experimentation on my part to implement this transition; see https://gtk-rs.org/gtk4-rs/stable/latest/book/main_event_loop.html for examples that helped steer me in the right direction.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As mentioned by @sdroege in gtk-rs/gtk4-rs#1521 (comment):
The text was updated successfully, but these errors were encountered: