You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On an AppWindow, when setting its WindowState to Fullscreen, then resetting it to Normal, the window doesn't revert the size and position; instead it resizes to the entire screen.
After debugging the code (of the master branch), this bug occurs because the AppWindow size is saved using the Win32 API after Avalonia has already changed the size by itself. Therefore, the restored size is wrong.
I'm about to create a PR that fixes this bug. Actually, according to my limited tests, only a conditional move of the OnPropertyChanged propagation (when the fullscreen is enabled) is needed. However, I might be mistaken, as I may not have reviewed all the AppWindow breaking changes that could prevent this fix.
The text was updated successfully, but these errors were encountered:
Commode3
changed the title
AppWindow is wrongly resize when changing Fullscreen to Normal mode
AppWindow is wrongly resized when changing Fullscreen to Normal mode
Jan 23, 2025
Describe the bug
On an
AppWindow
, when setting itsWindowState
toFullscreen
, then resetting it toNormal
, the window doesn't revert the size and position; instead it resizes to the entire screen.Lightest Sample Project to demonstrate the issue
AppWindowFullscreenBug.zip
Desktop/Platform specs
Additional context
This issue can be observed in the attached sample project (same as above).
After debugging the code (of the
master
branch), this bug occurs because theAppWindow
size is saved using the Win32 API after Avalonia has already changed the size by itself. Therefore, the restored size is wrong.I'm about to create a PR that fixes this bug. Actually, according to my limited tests, only a conditional move of the
OnPropertyChanged
propagation (when the fullscreen is enabled) is needed.However, I might be mistaken, as I may not have reviewed all the
AppWindow
breaking changes that could prevent this fix.The text was updated successfully, but these errors were encountered: