fix(hyprland): suppress "maximize" event at window creation

[cmleon51]

Description

Sometimes certain application windows send the "maximize" event at creation causing the window to be maximized regardless if there are other windows already open. For example whenever I opened Kitty and the mullvad browser when other windows were already opened they always got maximized and I had to minimize them manually.

This change to the hyprland.lua config file adds a window rule that omits the "maximize" event at window creation, a rule that already exists in the example lua configuration of Hyprland.

Type of change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that changes existing behavior)
• Refactor / internal cleanup
• Documentation
• Other

Related issues

Screenshots / video

Before this change we can see that if i open multiple instances of Kitty the new ones start maximized:

before.mp4

After my change I can open 3 kitty instances without them being maximized:

after.mp4

Checklist

• My code follows the conventions in CONTRIBUTING.md
• I have tested my changes locally
• New user-facing strings are wrapped in I18n.tr() with translator context, reusing existing terms where possible
• Go changes: ran make fmt, added/updated tests, make test passes, and go mod tidy is clean
• QML changes: ran make lint-qml with no new warnings
• I have opened a corresponding pull request in dlx-docs to document any new behaviors: https://github.com/AvengeMedia/DankLinux-Docs

[bbedward]

Is this ideal? I'm not sure about mullvad, but with newer kitty this is its intentional behavior and it suppresses it.

Kitty added the option to remember last state or something, and it's on by default. With this I assume, kitty's behavior wont be respected anymore

[cmleon51]

I think it's better than the current behaviour.

For example in kitty version 0.49.2 the only way that I have found for the terminal to not be maximized at startup is to add the option "start_as minimized" in the configuration file but then the problem still remains with the mullvad browser and, just found out, the tor browser.

One issue that comes up with this change with kitty is that the "start_as maximized" option won't work anymore since the signal will be ignored.

Still I think that by default the correct behaviour should be having windows correctly tiled instead of having "strange" behaviour only on certain windows.

If this doesn't want to be the default than my option would be to improve the "window rules" setting and, during the creation of a new rule, allow to choose one or multiple "suppress_event" options just like we can do with "Hyprland Options" now: