chore: use seperate Xresource keys for lock program

Author: SoumyaRanjanPatnaik

scripts/regolith-sway-clamshell

@@ -22,7 +22,7 @@ exit_with_error() {
 get_lid_close_cmd() {
   # Actions to take based on the value of wm.lidclose.action
   local DEFAULT_LOCK="gtklock --background $(trawlcat regolith.lockscreen.wallpaper.file /dev/null)"
-  local LOCK=$( trawlcat wm.program.lock "$DEFAULT_LOCK")
+  local LOCK=$( trawlcat wm.program.lock_sway "$DEFAULT_LOCK")
   local SLEEP=$( trawlcat wm.program.sleep "systemctl suspend" )
   local HIBERNATE=$( trawlcat wm.program.hibernate "systemctl hibernate" )
   local SHUTDOWN=$( trawlcat wm.program.shutdown "gnome-session-quit --power-off --no-prompt")

usr/share/regolith/i3/config.d/55_session_keybindings

@@ -40,8 +40,8 @@ bindsym $mod+$wm.binding.shutdown exec $wm.program.shutdown
 
 ## Session // Lock Screen // <> Escape ##
 set_from_resource $wm.binding.lock wm.binding.lock Escape
-set_from_resource $wm.program.lock wm.program.lock dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock
-bindsym $mod+$wm.binding.lock exec $wm.program.lock
+set_from_resource $wm.program.lock_i3 wm.program.lock_i3 dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock
+bindsym $mod+$wm.binding.lock exec $wm.program.lock_i3
 
 ## Session // Sleep // <><Shift> s ##
 set_from_resource $wm.binding.sleep wm.binding.sleep Shift+s

usr/share/regolith/sway/config.d/42_gtklock

@@ -1,4 +1,4 @@
 ## Session // Lock Screen // <> Escape ##
 set_from_resource $wm.binding.lock wm.binding.lock Escape
-set_from_resource $wm.program.lock wm.program.lock gtklock --background $(trawlcat regolith.lockscreen.wallpaper.file /dev/null)
-bindsym $mod+$wm.binding.lock exec $wm.program.lock
+set_from_resource $wm.program.lock_sway wm.program.lock_sway gtklock --background $(trawlcat regolith.lockscreen.wallpaper.file /dev/null)
+bindsym $mod+$wm.binding.lock exec $wm.program.lock_sway