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
eroc1990 has quit [Quit: Ping timeout (120 seconds)]
eroc1990 has joined #wayland
repetiti` has quit []
ybogdano has quit [Read error: Connection reset by peer]
ybogdano has joined #wayland
everfree_ has quit [Remote host closed the connection]
ybogdano is now known as Guest2156
Guest2156 has quit [Read error: Connection reset by peer]
ybogdano has joined #wayland
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
Lucretia has quit [Ping timeout: 480 seconds]
MrCooper_ has joined #wayland
MrCooper has quit [Read error: Connection reset by peer]
MrCooper__ has joined #wayland
MrCooper_ has quit [Read error: Connection reset by peer]
PuercoPop has joined #wayland
qpls has joined #wayland
<qpls>
when should one free objects passed to event callbacks?
<qpls>
I'
<qpls>
If I call destroy on the objects, there is still a possibility that an event callback will be made with a pointer to one of my data structures
<qpls>
what is the proper way to avoid this?
PuercoPop has quit [Ping timeout: 480 seconds]
ybogdano has quit [Ping timeout: 480 seconds]
fmuellner has quit [Ping timeout: 480 seconds]
adarshgm has joined #wayland
adarshgm1 has joined #wayland
adarshgm has quit [Read error: Connection reset by peer]
adarshgm has joined #wayland
bookworm has quit [Ping timeout: 480 seconds]
adarshgm1 has quit [Ping timeout: 480 seconds]
bookworm has joined #wayland
smallville7123 has joined #wayland
zebrag has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
zebrag has quit [Quit: Konversation terminated!]
Seirdy has quit [Ping timeout: 480 seconds]
Seirdy has joined #wayland
coleman has quit [Ping timeout: 480 seconds]
coleman has joined #wayland
sav10 has quit [Ping timeout: 480 seconds]
Leopold has joined #wayland
adarshgm1 has joined #wayland
adarshgm has quit [Ping timeout: 480 seconds]
markbolhuis has joined #wayland
smallville7123 has quit [Ping timeout: 480 seconds]
jgrulich has joined #wayland
Company has quit [Quit: Leaving]
adarshgm1 has quit [Read error: Connection reset by peer]
pH5 has joined #wayland
dcz_ has joined #wayland
smallville7123 has joined #wayland
pym_ has joined #wayland
coleman has quit [Ping timeout: 480 seconds]
<qpls>
nevermind, turns out the client library will suppress callbacks after destroy is called on the object
<qpls>
there was a bug in my code
<qpls>
I was calling the wrong destroy function T_T
<bryantchandler>
I'm looking for more information about why wayland doesn't include modifier information in pointer events. I found a reference from 2012 (https://lwn.net/Articles/483088/#:~:text=pointer%20axis%20events%20need%20modifiers%20(ctrl%2Dscroll%20eg)%2C%20but%20we%20either%0Aneed%20to%20send%20the%20modifier%20state%20with%20each%20axis/scroll%20event%20or%20send%0Akeys%20down%20on%20pointer_focus%20and%20subsequent%20key%20events...%20or%20just%20key
<bryantchandler>
%0Aevents%20for%20modifier%20keys...%20or%20for%20the%20non%2Drepeating%20subset%3F), but I haven't been able to find any more recent information on the topic.
<zamundaaa[m]>
Are you looking for historical information, or for a fix?
<bryantchandler>
I guess both. I did find that merge request, but it seemed to only cover trying to clarify the current behavior of managing modifiers completely separate from pointer events. I'm wondering why the modifier state isn't just included as a field on pointer events. That's a common approach and it seems like it would alleviate a lot of difficulties that arise from tracking modifier state separately.
<kennylevinsen>
wl_pointer and wl_keyboard are entirely separate, and tying them together by including wl_keyboard modifiers on wl_pointer events would break the abstraction
<kennylevinsen>
but making it so wl_keyboard modifiers are sent before wl_pointer click events does not seem unreasonable
<kennylevinsen>
(it is a little gross, but it also makes perfect sense, so eh)
<kennylevinsen>
this approach also aligns with how modifiers work for the wl_keyboard itself - we don't include modifiers in key events, so including them in mouse events would be odd
rgallaispou has left #wayland [#wayland]
kts has quit [Quit: Leaving]
___nick___ has quit []
___nick___ has joined #wayland
___nick___ has quit []
___nick___ has joined #wayland
rasterman has joined #wayland
rasterman has quit []
junaid has joined #wayland
mbalmer has joined #wayland
reductum has joined #wayland
rasterman has joined #wayland
MajorBiscuit has quit [Ping timeout: 480 seconds]
Florian[m] has quit []
bluepqnuin has quit []
<zzag>
kennylevinsen: purely from logical point of view, I could argue that sending wl_keyboard.modifiers to a surface with wl_pointer focus is also weird
MatrixTravelerbot[m]1 has quit []
<zzag>
the nice thing about wl_pointer.modifiers is that explicitly says that it's interested in keyboard modifiers
<zzag>
otherwise you are left to compositor implementation details
psydroid[m] has quit []
<zzag>
is that it explicitly*
anomalous_creator[m] has quit []
<kennylevinsen>
Absolutely agreed, but even weirder to integrate keyboard info in a wl_pointer event :D
<bryantchandler>
What if modifiers were split out so that both wl_keyboard and wl_pointer could depend on them. That would maintain the separation but allow the information to be included on both event types.
mbalmer has quit []
<tleydxdy>
I'd say there's never gonna be an fully clean abstraction since human interface are messy
junaid has quit [Remote host closed the connection]
aswar002 has quit [Remote host closed the connection]
aswar002 has joined #wayland
junaid has joined #wayland
<kennylevinsen>
bryantchandler: modifiers are physically and logically the property/state of a keyboard. That clients care about keyboard and mouse state simultaneously does not justify merging them.
floof58 is now known as Guest2287
floof58 has joined #wayland
<kennylevinsen>
that clients are unable to obtain keyboard state when they seemingly need it is separate, dealt with in the linked MR.
Guest2287 has quit [Ping timeout: 480 seconds]
ybogdano has quit [Read error: Connection reset by peer]
mvlad has quit [Remote host closed the connection]
ybogdano has joined #wayland
ofourdan has quit [Remote host closed the connection]
immibis has joined #wayland
immibis_ has quit [Ping timeout: 480 seconds]
ofourdan has joined #wayland
rasterman has quit [Quit: Gettin' stinky!]
___nick___ has quit [Ping timeout: 480 seconds]
bryantchandler has quit [Ping timeout: 480 seconds]
dcz_ has quit [Ping timeout: 480 seconds]
Guest2224 is now known as frytaped
bryantchandler has joined #wayland
danvet has quit [Ping timeout: 480 seconds]
junaid has quit [Ping timeout: 480 seconds]
ybogdano has quit [Read error: Connection reset by peer]
andyrtr_ has joined #wayland
ybogdano has joined #wayland
andyrtr has quit [Ping timeout: 480 seconds]
andyrtr_ is now known as andyrtr
andyrtr_ has joined #wayland
andyrtr has quit [Ping timeout: 480 seconds]
andyrtr_ is now known as andyrtr
Guest2208 is now known as DrNick
jmdaemon has joined #wayland
zebrag has quit [Ping timeout: 480 seconds]
zebrag has joined #wayland
floof58 is now known as Guest2299
floof58 has joined #wayland
Guest2299 has quit [Ping timeout: 480 seconds]
hardening has quit [Ping timeout: 480 seconds]
bryantchandler has quit [Ping timeout: 480 seconds]