We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is your feature request related to a problem? Please describe.
With the latest changes to our Linux implementations, it gets harder to spawn a thread, especially for dialogs.
In #2222 we fixed with the glib::MainContext
glib::MainContext
The big drawback with that is it runs on the main GtkThread, which means it locks the app run.
Having slow updater endpoints will cause the app to be slower to open (on Linux)
Describe the solution you'd like I'm not sure?
Describe alternatives you've considered N/A
Additional context
The text was updated successfully, but these errors were encountered:
@lemarier shouldn't the glib::MainContext be used only to render the dialog? that would keep the API call on a separate task.
Sorry, something went wrong.
I'll see if I can move the context usage to the dialog API itself.
refactor(core): handle dialog threading internally, closes #2223
57df90d
2088cd0
No branches or pull requests
Is your feature request related to a problem? Please describe.
With the latest changes to our Linux implementations, it gets harder to spawn a thread, especially for dialogs.
In #2222 we fixed with the
glib::MainContext
The big drawback with that is it runs on the main GtkThread, which means it locks the app run.
Having slow updater endpoints will cause the app to be slower to open (on Linux)
Describe the solution you'd like
I'm not sure?
Describe alternatives you've considered
N/A
Additional context
The text was updated successfully, but these errors were encountered: