Allow setting animation speed, curve, and extras in window/layer rules

[mononomori]

Describe the feature

Currently, window/layer rules support setting the animation type per parameter match. However, there is no way to set speed, curve, or extras (such as popin minimum percentage).

I'm requesting the ability to optionally include these settings when assigning animations via window/layer rules.

For example:

layerrule = animation, curve, speed, popin, extra, launcher 
 
windowrule = animation, curve, speed, popin, extra, class:^(some-app)$

Why would it be beneficial

Both setting per-window/layer animations and fine-tuning global animations by using a specific speed and creating custom curves are common use cases. However, there's currently a lack of cohesion between these two features, because setting an alternative animation for a given window or layer causes it to fall back to the default speed, curve, and extra settings. This leads to stylistic inconsistencies when you're using the same animation type via the animation tree, but with settings other than the default.

For instance, if I have all my popin animations using:

1, 3, mycurve, popin 60%

but then assign a specific window a popin animation via windowrule, it uses the default speed, curve, and extras, making it feel uncohesive with the rest of the setup.

Brought up prior to the new discussion system in: #5106, #5108

[Necronomison]

I too fully support this — being able to define speed, curve, and extras alongside animation types in windowrule and layerrule would make customization more consistent and flexible. Right now, falling back to defaults creates noticeable styling mismatches for my setup.

[vaxerski]

Although this is fine, and IIRC now possible with hyprutils' animations, the syntax won't work because of the commas. Come to think of it, spaces would work here too, no? I don't think anyone is a lunatic and uses spaces in their curve names.

[mononomori]

If the structure were such that the curve is always the last setting, would that help avoid issues with spaces in curve names? For example:

windowrule = animation <type> <extras> <speed> <curve>, match

Then users who don’t want to set everything could write:

windowrule = animation popin, class:^(app)$ → type

windowrule = animation popin 60%, class:^(app)$ → type + extra

windowrule = animation popin 60% 2, class:^(app)$ → type + extra + speed

windowrule = animation popin 60% 2 ease-in, class:^(app)$ → type + extra + speed + curve

This would make it a bit more flexible and maintain backwards compatibility with how people are currently setting animation rules.

Or it could just be enforced that curve names do not contain spaces.

Granted I did just do a short search through various people's configs on github and couldn't find anyone with spaces in their curve names lol.

[vaxerski]

extras have spaces though, that would not be great to parse. Anyways, I'm in favor of just giving people an L here if their curve has a space.

[vaxerski]

cool idea overall. Promoted #9894