v2.2 app window extends below dock if closed from full screen mode

[Maxdanger]

Hi Affinity,

Thanks so much for your hard work in releasing v2.2!

One thing I've immediately noticed (and in fairness I can see it's also present in the previous beta builds for 2.2 so sorry for not spotting this sooner) is that the app windows can open filling up the entire screen (ie extending below the dock) if you last used the application in full screen mode. Steps to reproduce are:

1. Open any app
2. Enter full screen mode
3. Quit the app while in full screen mode
4. Open the app again

The app won't open in full screen mode, but it will take up the entire height of the screen. If you quit the app not in full screen mode this issue does not persist.

Video showcasing the bug

 

This wasn't something present in 2.1 or previous so guessing it is a new bug with 2.2.

Thanks very much!
Max

[MikeTO]

Serif will undoubtedly reply but my personal recommendation is to hide your dock and then not bother with full-screen mode. The dock takes up valuable screen real estate that could be used to work on your documents. The dock is still there when it's hidden so mousing to the bottom of the screen will show it. In System Settings, go to Desktop & Dock and turn on "Automatically hide and show the Dock".

[Maxdanger]

Thanks for your suggestion. I've previously tried hiding the dock but I prefer to keep it when using other apps, it's only Affinity where I like to work in full screen as you say to have more screen real estate, so that's not the best solution for me

[Lee D]

@Maxdanger Thanks for the report, I've logged this to be looked into.

[Affinity Info Bot]

The issue "[macOS] Full screen app then close and reopen causes UI to appear behind OS menu bar and dock." (REF: AF-315) has been fixed by the developers in internal build "2.4.0.2185".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.