ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
nerdopolis has quit [Ping timeout: 480 seconds]
manuel1985 has joined #wayland
nerdopolis has joined #wayland
ikhouvanL has quit [Quit: Page closed]
kasper93 has quit [Ping timeout: 480 seconds]
mclasen has quit []
mclasen has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
manuel_ has joined #wayland
manuel1985 has quit [Remote host closed the connection]
<peelz>
and unfortunately that prevents standalone screen lockers (e.g swaylock) to turn off the monitors after a period of inactivity :(
kts has joined #wayland
<emersion>
that's the whole point
<emersion>
idle-inhibit exists for preventing screen lockers from kicking in while you're watching a movie
<peelz>
right, except it would be nice to ignore inhibition if swaylock is already active
<peelz>
so dpms can work on the lockscreen
mclasen has quit [Ping timeout: 480 seconds]
<peelz>
if I have an inhibitor active and I manually trigger the lockscreen, swayidle won't be able to turn off the outputs after a timeout
<emersion>
that's arguably a sway issue, it should ignore inhibitors which are not visible on-screen
<peelz>
ah I see, create_inhibitor() takes a surface
kts has quit [Ping timeout: 480 seconds]
rasterman has quit [Quit: Gettin' stinky!]
<peelz>
emersion, if sway were to ignore inhibitors that aren't on screen, how would one go about creating an inhibitor that isn't associated with a window (e.g a CLI tool)? sorry for the uneducated question, I'm still quite new to wayland internals
<emersion>
CLI tools don't use wayland
<peelz>
well there's wl-clipboard (wl-copy/wl-paste)
<peelz>
it uses an invisible surface to do clipboard stuff afaik
<emersion>
sway has commands to tweak the idle inhibition, so one could use that from a script
<emersion>
no, it uses a wayland protocol for clipboard managers
<peelz>
huh? so wl-clipboard doesn't use wayland but it uses the wayland clipboard protocol?
<emersion>
we use "a wayland protocol" as an abbreviation of "a wayland protocol extension", it's still just wayland
<peelz>
right, but you said "CLI tools don't use wayland"
<peelz>
by that definition, doesn't wl-clipboard (which uses the wayland clipboard protocol extension) use wayland?
neniagh has quit [Ping timeout: 480 seconds]
<peelz>
sorry, I think I got confused. I see you were talking about how wl-clipboard uses the wayland clipboard protocol (which doesn't use any surfaces)
<peelz>
I'll take a look at sway's inhibit_idle command. That might just be what I need. Thanks :D
neniagh has joined #wayland
<kennylevinsen>
peelz: wl-clipboard is a hack and an outlier. It creates a window briefly to get permission to use the clipboard it it can't get access to the clipboard management protocols
<kennylevinsen>
in the context of sway, CLI tools usually use sway's IPC or call swaymsg
systwi has quit [Ping timeout: 480 seconds]
<peelz>
kennylevinsen, ah gotcha. I thought I was misremembering about the window thing. Why does it need to create a window? Is it a protocol requirement? I'm trying to find an answer on wayland.app
<kennylevinsen>
You are not allowed access to the clipboard unless you have focus
<kennylevinsen>
and you can't have focus without a window
<kennylevinsen>
gtk_primary_selection is deprecated and replaced by the primary selection protocol
<peelz>
what's the protocol for the clipboard (not primary selection)?
<kennylevinsen>
wlr data control is a privileged clipboard management protocol that not all compositors support, meant for writing (privileged) clipboard managers
<kennylevinsen>
peelz: wl_data_offer/source/device/device_manager in the core protocol
<peelz>
right, that's what I was getting at. It's not implemented by gnome-shell for example
jtbx has joined #wayland
<peelz>
oh alright
<peelz>
thanks for answering my questions, I appreciate it
rv1sr has quit [Ping timeout: 480 seconds]
AnuthaDev has joined #wayland
rv1sr has joined #wayland
azerov has quit []
azerov has joined #wayland
systwi has joined #wayland
fossdd has quit [Ping timeout: 480 seconds]
kts has joined #wayland
mclasen has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
Leopold has quit [Remote host closed the connection]