ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
fmuellner has quit [Ping timeout: 480 seconds]
guru__ has joined #wayland
guru_ has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
Brainium has quit [Quit: Konversation terminated!]
garnacho has quit [Ping timeout: 480 seconds]
aknot has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
glennk has joined #wayland
lbia has quit [Remote host closed the connection]
lbia has joined #wayland
mxz__ has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
mxz___ has joined #wayland
mxz has quit [Ping timeout: 480 seconds]
mxz___ is now known as mxz
mxz_ has quit [Ping timeout: 480 seconds]
aknot has quit [Remote host closed the connection]
Guest8360 has quit [Remote host closed the connection]
cool110 has joined #wayland
cool110 is now known as Guest8432
ity has quit [Remote host closed the connection]
ity has joined #wayland
cvmn has quit [Remote host closed the connection]
caveman has joined #wayland
caveman has quit [Remote host closed the connection]
<kennylevinsen>
danieldg: only tiling compositors need to synchronize toplevels, and even then it's just a wait until ack_configure. Writing a client with subsurfaces, in particular desync and externally controlled ones, correctly so that the toplevel doesn't appear glitchy is another problem altogether...
leon-anavi has joined #wayland
<narodnik>
hey is there a simple code sample showing how to copy/paste from the clipboard?
<pq>
narodnik, I would say that clipboard handling at the Wayland protocol level of asbtraction is fundamentally complicated.
<kode54>
narodnik: the copying app *is* the clipboard
<pq>
you'll also need a visible window in the same client
<kode54>
wl-copy lives for the life of the copy
<pq>
you'll be able to copy/paste when your visible window gets input events that you can refer to
agd5f has joined #wayland
<pq>
narodnik, the transport is writing/reading a pipe, and the mime-type negotiation is needed to agree on the data format first. Is that what you referred to as complicated?
kts has joined #wayland
<pq>
writing/reading a pipe without freezing the app is its own chore
agd5f_ has quit [Ping timeout: 480 seconds]
rasterman has joined #wayland
<narodnik>
i have a visible window, and a wayland client
garnacho has joined #wayland
<narodnik>
and the seat .etc, but then i want to just copy/paste text from the clipboard
<narodnik>
the mime type is just simply text
<narodnik>
was wondering if there's a short code sample rather than having to reverse engineer wl-clipboard
mripard_ is now known as mripard
<pq>
it's not a short code
<pq>
you'll have to deal with the pipe
<pq>
Weston's clients/window.c has some self-standing code, too, but I'm looking if there is an obvious entry point you could start to untangle it from...
<kennylevinsen>
narodnik: bind the wl_data_device_manager, get the wl_data_device, accept the incoming wl_data_offer's appropriate mime type, and send an fd over receive to have the data written to, then destroy the offer
<kennylevinsen>
But handling the pipe to be used as fd takes a bit of code
<kennylevinsen>
To not risk blocking the whole client for an indeterminate amount of time
<narodnik>
thanks a lot, appreciate the help + any further advice
<pq>
clients/window.c display_add_data_device() binds the data device manager, so that's a starting point.
<narodnik>
ty, appreciated
<pq>
input_set_selection() seem to be the "copy/cut" function
kts has quit [Ping timeout: 480 seconds]
<narodnik>
gotcha thanks
feaneron has joined #wayland
lbia has quit [Ping timeout: 480 seconds]
vsyrjala has quit [Ping timeout: 480 seconds]
kts has joined #wayland
lbia has joined #wayland
feaneron has quit [Remote host closed the connection]
kts has quit [Ping timeout: 480 seconds]
fmuellner has joined #wayland
kts has joined #wayland
vsyrjala has joined #wayland
feaneron has joined #wayland
nerdopolis has joined #wayland
kts has quit [Ping timeout: 480 seconds]
feaneron has quit [Quit: feaneron]
agd5f_ has joined #wayland
agd5f has quit [Ping timeout: 480 seconds]
kts has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
mvlad is now known as Guest8466
Guest8466 has quit [Ping timeout: 480 seconds]
mvlad has joined #wayland
nerdopolis has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
kts_ has joined #wayland
kts has quit [Ping timeout: 480 seconds]
kts_ has quit []
feaneron has joined #wayland
rv1sr has joined #wayland
feaneron has quit [Read error: No route to host]
feaneron has joined #wayland
lbia has quit [Ping timeout: 480 seconds]
guru__ has quit [Remote host closed the connection]
<pq>
Funny how P3D65 is supposed to have peak encoded luminance of 48 cd/m². Maybe it's a different P3D65 from Apple's...
<pq>
also funny that P3 implies power-law TF exponent 2.6
mvlad has quit [Remote host closed the connection]
mvlad has joined #wayland
kts has joined #wayland
mclasen has quit [Remote host closed the connection]
glennk has quit [Read error: Connection reset by peer]
mclasen has joined #wayland
chamlis has quit [Remote host closed the connection]
chamlis has joined #wayland
mart has quit [Quit: Konversation terminated!]
bittin is now known as travel_luna
feaneron has quit [Quit: feaneron]
agd5f_ has quit [Read error: No route to host]
agd5f has joined #wayland
agd5f has quit [Remote host closed the connection]
agd5f has joined #wayland
TheCaptain82970403198578471379 has quit [Ping timeout: 480 seconds]
tlwoerner_ has quit []
tlwoerner has joined #wayland
glennk has joined #wayland
Leopold_ has joined #wayland
kts has quit [Quit: Konversation terminated!]
lbia has joined #wayland
rasterman has quit [Quit: Gettin' stinky!]
feaneron has joined #wayland
mart has joined #wayland
Brainium has joined #wayland
Narrat has joined #wayland
kinlo has quit [Remote host closed the connection]
thalos has joined #wayland
<thalos>
Hi! Maybe a stupid question but, I just switched to wayland (running hyprland as compositor), I can't seem to find any log file or status, like Xorg.log in order to see how wayland has detected my hardware. Am I missing something?
<bl4ckb0ne>
that's a hyprland question, compositors manage their own logs
<bl4ckb0ne>
wayland has nothing to do with it, it's just an protocol