Skip to content
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

Display very early errors in GUI #1010

Merged
merged 1 commit into from
Mar 31, 2024
Merged

Conversation

tleedjarv
Copy link
Contributor

Previously, errors during very early GUI init process, before the main window was created, would not be displayed in the GUI. The user would not know what was happening because the GUI would just not start. The only way the user would see the error was to read stderr, if available.

This patch makes it possible to display very early errors in GUI, as long as GTK init has been successful. If the GTK init itself fails then the user still must have access to stderr to understand what happened.

Previously, errors during very early GUI init process, before the main
window was created, would not be displayed in the GUI. The user would
not know what was happening because the GUI would just not start. The
only way the user would see the error was to read stderr, if available.

This patch makes it possible to display very early errors in GUI, as
long as GTK init has been successful. If the GTK init itself fails then
the user still must have access to stderr to understand what happened.
@gdt gdt merged commit f55cf70 into bcpierce00:master Mar 31, 2024
29 checks passed
@tleedjarv tleedjarv deleted the gui-fatalerr branch March 31, 2024 20:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants