Enable hyprlock input animations

[FilipHarald]

Adds animation so that long passwords still gives visual feedback on inputs. This is intentionally a small commit to be as little of disruption as possible. Just adding animation to password input so that you can visually see your key strokes.

I'd be happy to give the orb-animation a try as described in #6130 but I'm not sure that is something most users want.

Before and after videos below of this PR.

existing_no_visual_feedback.mp4

new_visual_feedback.mp4

[Copilot]

Pull request overview

This PR enables Hyprlock input animations in the default hyprlock.conf so users get visual feedback while typing (especially helpful for long passwords), without broader lock screen behavior changes.

Tip

If you aren't ready for review, convert to a draft PR.
Click "Convert to draft" or run gh pr ready --undo.
Click "Ready for review" or run gh pr ready to reengage.

Changes:

• Enable Hyprlock animations by setting animations.enabled = true in the default config.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[brink-lab]

Hi @FilipHarald,
While this is a good idea, I believe Omarchy is ditching hyprlock in favour of a quickshell based solution for the upcoming Omarchy 4 release.

[FilipHarald]

Hi @FilipHarald, While this is a good idea, I believe Omarchy is ditching hyprlock in favour of a quickshell based solution for the upcoming Omarchy 4 release.

Thanks for pointing this out! I made a PR here instead, not sure if it's correct branch though? #6137

Also, @brink-lab , thank you for just giving me a nudge to embark on the journey to use the dev-channel for trying omarchy v4 and quickshell. What a delight! Already starting to play around with the quickshell configs 😄

[FilipHarald]

This PR can be closed in favor of #6137

[brink-lab]

Great work, and I love your drive :D. This project has been a great learning experience for me as well.

David is very active in the quattro branch right now, so I think you have placed your pull request correctly. If not, don't sweet it. It can always be reassigned or merged later.