-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
splash screen without forced keep-above #18236
Closed
+46
−41
Closed
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
032b378
rework splash screen to avoid keep-above
ralfbrown 9fe6e2a
raise splash screen after realizing main window
ralfbrown acfa14e
don't restore stored window config until after realizing main window
ralfbrown de3c16b
add more progress updates per dterrahe
ralfbrown File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If done in this order, I get, on windows
if instead I do
then the splash screen is instantaneously replaced by the window in its final location.
The
gtk_widget_show_all
andgtk_widget_set_visible(FALSE)
(=hide) in_init_widgets
is not needed.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing the
gtk_widget_show_all
from_init_widgets
restults in half a dozen assertion failure messages from Gdk, because various items in the main window haven't been realized yet (they don't get created until the main window is initially shown).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not make the code more robust by adding the appropriate checks rather than implementing more workarounds?
dterrahe@40fce3c generates no warnings for me, on debian (x&wayland, under WSL2) and windows.
Unfortunately, if
dt_gui_gtk_load_config
is moved beforeshow_all
, when restoring a maximized state, the application thinks it is maximized, but the window manager disagrees. Even ifdt_gui_gtk_load_config
is executed both before and aftershow_all
(presumably for an "already maximized" window, maximize is a noop). So there is still a very minimal/undiscernible amount of flashing when showing the screen. But no second or so gap between the splash disappearing and the main window appearing and also no overlap.EDIT: if you still do see assertions, please let me know which so I can look into them.