ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput | register your nick to speak
rasterman has quit [Quit: Gettin' stinky!]
apol[m] has joined #wayland
sndb has quit [Ping timeout: 480 seconds]
Eighth_Doctor has joined #wayland
sndb has joined #wayland
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
DrNick has joined #wayland
DrNick is now known as Guest1834
fmuellner has quit [Ping timeout: 480 seconds]
shashank1202 has joined #wayland
[old]freshgumbubbles[m] has joined #wayland
rails[m] has joined #wayland
Levans has joined #wayland
boistordu_old has quit [Ping timeout: 480 seconds]
idkrn[m] has joined #wayland
mooff- has joined #wayland
x[m] has joined #wayland
reactormonk[m] has joined #wayland
niecoinny[m] has joined #wayland
shashank1202 has quit [Quit: Connection closed for inactivity]
zebrag has quit [Quit: Konversation terminated!]
gnustomp[m] has joined #wayland
sndb is now known as Guest1857
sndb has joined #wayland
Guest1857 has quit [Read error: Connection reset by peer]
<pq>
jadahl, I could nitpick about "buffer offset" giving the idea of a value in bytes, but I don't want to tell you to go to paint shop at this stage.
<jadahl>
i guess "offset" has a default meaning depending on what direction you fall onto it from
<jadahl>
offset in geometry is one thing, offset in bytes is another
<pq>
in the spec, you have the literal phrase "buffer offset"
<emersion>
"content offset" mayeb better?
<jadahl>
ah, heh, buffer coordinate space offset I guess :P
<SardemFF7>
and the request summary does say “contents offset” instead :-)
<pq>
displavement or translation?
<pq>
*displacement
<jadahl>
the attach() x/y is referred to as offset
<jadahl>
or maybe that is something I added
<pq>
well, the offset is not in buffer coordinate space, no
<jadahl>
well we haven't moved into the shed, so can still repaint it a couple of more times
<emersion>
i think offset is fine, just don't use it with the word "buffer"
<emersion>
since it's in surface-local coords
<pq>
I can go with "surface offset" or even "content offset" I think.
<emersion>
"surface offset" is a bit misleading
<emersion>
since what this does is role-dependant
<jadahl>
what a surface means also involves viewporter and what not
<pq>
this is wayland core FWIW - it does not know about viewporter
<pq>
viewporter also changes the meaning of "buffer corner"
<pq>
jadahl, there you go, sent a green a light.
slattann has quit []
<jadahl>
thanks
slattann has joined #wayland
gryffus has joined #wayland
slattann has quit []
slattann has joined #wayland
txtsd has quit [Quit: WeeChat 3.3]
d_ed has joined #wayland
anarsoul has quit [Read error: Connection reset by peer]
anarsoul has joined #wayland
slattann has quit []
slattann has joined #wayland
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
fmuellner has joined #wayland
slattann has quit []
haritz is now known as alarumbe
muhomor has quit [Remote host closed the connection]
muhomor has joined #wayland
flibitijibibo has quit [Remote host closed the connection]
<zubzub>
it is set in the xdg toplevel surface state though but it seems it's not queried anywhere
gryffus has quit [Remote host closed the connection]
<zubzub>
it does seem like the resize implementation makes use of max & min size, but since xdg does not expose it, it fallbacks to (0,0)
slattann has joined #wayland
NeoCron has joined #wayland
txtsd has joined #wayland
slattann has quit []
leon-p_ has joined #wayland
leon-p has quit [Ping timeout: 480 seconds]
txtsd has quit [Ping timeout: 480 seconds]
slattann has joined #wayland
rgallaispou has quit [Read error: Connection reset by peer]
shashank1202 has joined #wayland
tlwoerner has quit [Read error: Connection reset by peer]
tlwoerner has joined #wayland
ppascher has joined #wayland
xexaxo has quit [Read error: Connection reset by peer]
xexaxo has joined #wayland
d_ed has quit [Ping timeout: 480 seconds]
Narrat has joined #wayland
moodman has joined #wayland
<moodman>
Hello, I've been working on a wayland client and am having issues with the client respecting the borders I have set from within sway
<moodman>
I am setting both the app id and title, it feels like I am missing some xdg thing
<kennylevinsen>
moodman: define "respecting the borders"
<kennylevinsen>
Look at xdg_decoration, and note that sway allows you to override the client decoration choice.
<kennylevinsen>
(See `man 5 sway` and look for "border toggle")
<moodman>
thank you, by respecting border I mean that normally my windows have a couple pixel black border. But they dont show up on my program.
<moodman>
xdg_decoration is what I was looking for I think
<moodman>
one other question which I am pretty sure I know the answer to, there isn't a way for a client to move a mouse within the boundry of its own window programatically is there?
xexaxo has quit [Read error: No route to host]
slattann has quit []
hendursa1 has quit []
hendursaga has joined #wayland
lyudess has quit []
Lyude has joined #wayland
<kennylevinsen>
moodman: not officially, there are some nasty hacks that work for now but wasn't meant to
<moodman>
got it, thanks for the help :)
dcz_ has quit [Ping timeout: 480 seconds]
Seirdy has quit [Quit: exiting 3.2]
tzimmermann has quit [Quit: Leaving]
leon-p_ has quit [Remote host closed the connection]