SafeEyes
SafeEyes copied to clipboard
slgobinath
Use 'Layer' for Break screen instead of 'Window'
Is your feature request related to a problem? Please describe. Currently the break screen is treated as "Window" in D.E which means that user can just swipe to different workspace and break screen will no longer show.
Describe the solution you'd like Create Layer.
Additional context https://wiki.hyprland.org/Configuring/Window-Rules/#layer-rules https://wayland.app/protocols/wlr-layer-shell-unstable-v1
Are layers specific to hyprland?
On Sat, Apr 12, 2025, 2:49 AM KAGEYAM4 @.***> wrote:
Is your feature request related to a problem? Please describe. Currently the break screen is treated as "Window" in D.E which means that user can just swipe to different workspace and break screen will no longer show.
Describe the solution you'd like Create Layer.
Additional context https://wiki.hyprland.org/Configuring/Window-Rules/#layer-rules https://wayland.app/protocols/wlr-layer-shell-unstable-v1
— Reply to this email directly, view it on GitHub https://github.com/slgobinath/SafeEyes/issues/700, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAXL2XARPW6SDZKKCCNHY3L2ZCZRDAVCNFSM6AAAAAB27VXSECVHI2DSMVQWIX3LMV43ASLTON2WKOZSHE4TAMRYGUZTSMQ . You are receiving this because you are subscribed to this thread.Message ID: @.***> KAGEYAM4 created an issue (slgobinath/SafeEyes#700) https://github.com/slgobinath/SafeEyes/issues/700
Is your feature request related to a problem? Please describe. Currently the break screen is treated as "Window" in D.E which means that user can just swipe to different workspace and break screen will no longer show.
Describe the solution you'd like Create Layer.
Additional context https://wiki.hyprland.org/Configuring/Window-Rules/#layer-rules https://wayland.app/protocols/wlr-layer-shell-unstable-v1
— Reply to this email directly, view it on GitHub https://github.com/slgobinath/SafeEyes/issues/700, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAXL2XARPW6SDZKKCCNHY3L2ZCZRDAVCNFSM6AAAAAB27VXSECVHI2DSMVQWIX3LMV43ASLTON2WKOZSHE4TAMRYGUZTSMQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>
From what I can see, the Layer protocol is meant to be for things deeply integrated into the desktop environment, like statusbars and wallpapers. It's also not supported by GNOME/Mutter, so we'd have to either find something similar there, or keep the Window approach around, or drop support for GNOME. Also, I'm pretty sure we'd have to basically drop GTK and hand roll our own implementation. None of these options look feasible to me, unfortunately. If you think this is possible to implement, feel free to make a PR and we can discuss the specifics there - I don't think I know enough to implement this myself.
On another note: We try to avoid this issue of switching workspaces by using GtkWindow.inhibit_system_shortcuts(), which on Wayland uses the Keyboard Shortcuts Inhibit Protocol - which Hyprland does support, and which does work for me on KDE to block me from switching desktops using keyboard shortcuts. Is there a way to make Hyprland respect this when swiping as well? (I assume this means eg. a three-finger-swipe?)
Is there a way to make Hyprland respect this when swiping as well? (I assume this means eg. a three-finger-swipe?)
Will have to ask hyprland dev
SafeEyes Stable (v2.2.3) KDE - worspace change using three-finger-swipe and using keyboad shortcut --> safeeyes stays onscreen whole time Hyprland - workspace change using three-finger-swipe and using keyboad shortcut --> safeyes only stays on one workspace
SafeEyes git KDE - workspace change using three-finger-swipe no longer works , keyboard shortcut works Hyprland - workspace change using three-finger-swipe still does not work, keyboard shortcut now works
~~Weird behaviour in git version --> on hyprland with my safeeyes config from stable version creates buggy behaviour in safeeyes git where the break-window no longer shows up.~~
Hyprland will also inhibit gesture under shortcut inhibitors - https://github.com/hyprwm/Hyprland/issues/11546
This will fix the problem under hyprland.