fix(wayland): fix the wrong initial window inner size on GTK + Wayland. #1054
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.
Purpose
Fix the wrong initial window inner size on GTK + Wayland. Fixes #929
Related: #984
Troubleshooting
I write a minimal GTK app with a custom title bar using the
gtk-rs
crate to reproduce the issue. And found that the initial window inner size is correct on Wayland. So I assume the issue is related to the Tao's usage of GTK.By bisecting the Tao's code in
platform_impl::linux::Window::new()
method, I found that the issue is related to thewindow.set_visible(attributes.visible);
line. If I comment out this line, the initial window inner size is correct on Wayland.Then I tried to add this line to the GTK app I wrote before, and found that the issue is reproduced. So I think the issue is related to the
set_visible
method call on window.Below is the minimal code I used to reproduce the issue. Toggle the
win.set_visible(true)
to see the difference between the two.Solution
Looks like the
set_visible
call is unnecessary, because theshow_all
method will show the window. So, we can remove theset_visible
call to fix the issue.