Fixed an issue with X11 window state judgment caused by the order of Atoms.

[walterlv]

What does the pull request do?

Let's see a atom list of a sample Avalonia window:

_NET_WM_STATE_MAXIMIZED_VERT, _NET_WM_STATE_MAXIMIZED_HORZ, _NET_WM_STATE_HIDDEN, _NET_WM_STATE_FULLSCREEN

Before this PR, the WindowState.Maximized condition will be true first and return. So the window WindowState property will be set to Maximized but the window is actually Hidden.

After this PR, the WindowState.Hidden condition will be checked first and return. So the window WindowState property will be set to Minimized and the window is actually Hidden.

What is the current behavior?

There is only one loop to check the atom list. The order of atoms will affect the result of the window state judgment.

What is the updated/expected behavior with this PR?

The window state judgment is more accurate.

How was the solution implemented (if it's not obvious)?

I changed the loop from a single one to per-atom specific.

Checklist

• Added unit tests (if possible)?
• Added XML documentation to any related classes?
• Consider submitting a PR to https://github.com/AvaloniaUI/avalonia-docs with user documentation

Breaking changes

Nothing.

Obsoletions / Deprecations

Fixed issues

[avaloniaui-bot]

You can test this PR using the following package version. 11.2.999-cibuild0051654-alpha. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]