Skip to content
This repository has been archived by the owner on Jun 8, 2021. It is now read-only.

Acquire the default MainContext when initializing GTK #780

Merged
merged 2 commits into from
Feb 10, 2019
Merged

Acquire the default MainContext when initializing GTK #780

merged 2 commits into from
Feb 10, 2019

Conversation

sdroege
Copy link
Member

@sdroege sdroege commented Feb 10, 2019

It is required for GTK to be able to own the default main context on the
thread that initialized it, among other things to run its main loop on
that.

Make this more explicit by already acquiring it here during
initialization. This also ensures that other API that checks that this
very thread owns the main context works out of the box.

This depends on gtk-rs/glib#447

It is required for GTK to be able to own the default main context on the
thread that initialized it, among other things to run its main loop on
that.

Make this more explicit by already acquiring it here during
initialization. This also ensures that other API that checks that this
very thread owns the main context works out of the box.
@EPashkin
Copy link
Member

Good idea, thanks, 👍

@GuillaumeGomez
Copy link
Member

Restarted CI.

@sdroege
Copy link
Member Author

sdroege commented Feb 10, 2019

This will be green once #779 is merged.

@GuillaumeGomez
Copy link
Member

Restarted CI.

@sdroege
Copy link
Member Author

sdroege commented Feb 10, 2019

@GuillaumeGomez green apart from appveyor being broken :) I'll fix that later... but it's worrying that gtk tests don't work there. The setup seems broken.

@GuillaumeGomez
Copy link
Member

appveyor worked, travis didn't. Is it expected?

@GuillaumeGomez GuillaumeGomez merged commit 9f614e4 into gtk-rs:master Feb 10, 2019
alex179ohm pushed a commit to alex179ohm/gtk that referenced this pull request Oct 21, 2019
Use Option<&T> instead of &Option<T> for signal callback parameters
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants