Proper Dbus events for lock hint

[JunaidQrysh]

Description

Reference - kde screen locker Main Issue

Hyprlock should set the LockedHint on both lock and unlock as It is necessary for apps depending on the lock state.

[PointerDilemma]

Yeah I have argued against this in the past, as from my point of view it is the compositor that should set the locked hint. More simple lock screen applications like swaylock don't want to add it. See https://github.com/swaywm/swaylock/issues/382.

However in Hyprland, we also don't want dbus stuff I think, so in a sense hypridle (and swayidle for that matter) exists to keep the dbus stuff out of the compositor.

Since we now have hyprland-lock-notify, we can totally add the locked hint to hypridle and have it work for all lockscreen clients using Hyprland + hypridle.

But I am not 100% confident on this. Since we have fingerprint support in hyprlock, which already uses dbus, we could also just bite the bullet.

So the 2 options are:

• add it to hypridle
• add it to hyprlock

Any opinions @vaxerski, OP?

[vaxerski]

hypridle can use the locked hint for setting dbus props

I dont mind dbus in hyprland