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
coleman has quit [Ping timeout: 480 seconds]
coleman has joined #wayland
ybogdano has joined #wayland
coleman has quit [Ping timeout: 480 seconds]
sozuba has joined #wayland
coleman has joined #wayland
ChengAnXu has joined #wayland
MrCooper has quit [Remote host closed the connection]
MrCooper has joined #wayland
Moprius has quit [Remote host closed the connection]
<ChengAnXu>
hello?
<ChengAnXu>
有人吗？
<smallville7123>
hi
<i509VCB>
Hello! Ask away if you have any questions
agd5f has quit [Read error: Connection reset by peer]
<ChengAnXu>
How can I know whether my system is using x server or wayland compositer?
<soreau>
`echo $WAYLAND_DISPLAY` in a terminal from the wayland session might be one way
<ChengAnXu>
thank you
coleman has quit [Ping timeout: 480 seconds]
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
<smallville7123>
welp, we got 33 of 90 files compiling :)
<smallville7123>
wayland-shm, event_loop, and wayland-client are failing to compile still :)
floof58 has quit [Remote host closed the connection]
floof58 has joined #wayland
slattann has joined #wayland
fmuellner has quit [Ping timeout: 480 seconds]
<RAOF>
Hm. Does wl_touch.down generate an implicit (touch) grab? I would expect it to, and I'd expect that you could use it for the serial in wl_data_device.start_drag(), but it's not clear.
<RAOF>
Also, absolutely no clients I can find support drag-and-drop with touch input, which also surprises me and suggests that maybe there is not an implicit grab on touch down?
slattann1 has joined #wayland
slattann1 has left #wayland [#wayland]
slattann has quit [Ping timeout: 480 seconds]
slattann1 has joined #wayland
julio7359 has joined #wayland
ChengAnXu has quit [Remote host closed the connection]
sav10 has joined #wayland
Company has quit [Quit: Leaving]
cvmn has joined #wayland
Serus has quit [Read error: Connection reset by peer]
Serus has joined #wayland
cvmn has quit [Remote host closed the connection]
cvmn has joined #wayland
sav10 has quit []
cvmn has quit [Ping timeout: 480 seconds]
ChengAnXu has joined #wayland
ChengAnXu has left #wayland [#wayland]
sav10 has joined #wayland
sav10 has quit [Read error: Connection reset by peer]
katp32 has joined #wayland
katp32 is now known as Guest1954
Guest1954 is now known as katp32
<katp32>
hi, why does trying to build wayland-scanner give an error about pkg-config not being able to find wayland-scanner. that's kind of the point of building wayland-scanner
katp32 has left #wayland [#wayland]
nerdopolis has quit [Ping timeout: 480 seconds]
coleman has joined #wayland
sozuba_tmp has joined #wayland
sozuba has quit [Ping timeout: 480 seconds]
sozuba has joined #wayland
kts has joined #wayland
sozuba_tmp has quit [Ping timeout: 480 seconds]
junaid has joined #wayland
tzimmermann has joined #wayland
rv1sr has joined #wayland
julio7359 has quit [Ping timeout: 480 seconds]
sav10 has joined #wayland
junaid has quit [Ping timeout: 480 seconds]
jgrulich has joined #wayland
danvet has joined #wayland
genpaku has quit [Remote host closed the connection]
genpaku has joined #wayland
mvlad has joined #wayland
hardening has joined #wayland
rasterman has joined #wayland
manuel1985 has joined #wayland
MajorBiscuit has joined #wayland
cool110 has quit [Ping timeout: 480 seconds]
cool110 has joined #wayland
<wlb>
weston/main: Philipp Zabel * libweston, backends: store backend pointer in struct weston_head https://gitlab.freedesktop.org/wayland/weston/commit/746a03068e7c include/libweston/libweston.h libweston/backend-drm/drm-internal.h libweston/backend-drm/drm.c libweston/backend-headless/headless.c libweston/backend-rdp/rdp.c libweston/backend-rdp/rdp.h libweston/backend-vnc/vnc.c libweston/backend-wayland/wayland.c lib
mvlad has quit [Remote host closed the connection]
mvlad has joined #wayland
MajorBiscuit has quit [Ping timeout: 480 seconds]
melissawen_ has left #wayland [#wayland]
melissawen has joined #wayland
Moprius has joined #wayland
MajorBiscuit has joined #wayland
devilhorns has joined #wayland
pbeta has quit [Quit: WeeChat 3.0]
<zamundaaa[m]>
RAOF: Dolphin does drag and drop with touch, so it's definitely possible
Moprius has quit [Quit: bye]
slattann1 has quit [Ping timeout: 480 seconds]
cool110 has quit [Remote host closed the connection]
cool110 has joined #wayland
sav10 has quit []
fmuellner has joined #wayland
nerdopolis has joined #wayland
paulk-ter has quit [Ping timeout: 480 seconds]
kts has quit [Quit: Leaving]
agd5f has joined #wayland
kts has joined #wayland
Company has joined #wayland
jgrulich has quit [Remote host closed the connection]
agd5f_ has joined #wayland
agd5f_ has quit [Remote host closed the connection]
agd5f_ has joined #wayland
agd5f_ has quit [Remote host closed the connection]
agd5f has quit [Ping timeout: 480 seconds]
agd5f has joined #wayland
floof58 has quit [Ping timeout: 480 seconds]
floof58 has joined #wayland
<bl4ckb0ne>
is there any protocol that defines somewhat of a state machine?
<vyivel>
what are you trying to do
manuel1985 has quit [Ping timeout: 480 seconds]
<bl4ckb0ne>
im designing the protocol for the xr hand tracking for wxrc
<bl4ckb0ne>
the compositor recognizes gestures from the hand (neutral, fist, point, pinch) and sends them to the client
<bl4ckb0ne>
basically, its a finish state machine
<pq>
bl4ckb0ne, does wl_touch count as a state machine?
<bl4ckb0ne>
but im stuck at how to send them to the client
<pq>
also wl_keyboard events drive a state machine (libxkbcommon)
<bl4ckb0ne>
its close to what I want to achieve, but 3 events per gesture seems a lot
<pq>
3 events?
<bl4ckb0ne>
all gestures have the same data (vec3 position, quat orientation)
<bl4ckb0ne>
down, motion, up
<pq>
aaha
<pq>
wl_pointer, then? button-down/up would be your neutral/fist/point/pinch?
<pq>
plus frame events to tie things into a packet
<bl4ckb0ne>
hm that could do it
<bl4ckb0ne>
a gesture event with the gesture and the state
<pq>
I'm not sure I see much of a state machine there really, more like updates to a single state that has many arguments
<bl4ckb0ne>
and a `pose` event that sends data
<bl4ckb0ne>
thats where it gets weird
<pq>
or a single record more than a state
<bl4ckb0ne>
all 4 states have the same type of data, but interpreted differently
<bl4ckb0ne>
neutral/fist is the position of the palm
<bl4ckb0ne>
pinch is the position between the thumb tip and index tip
<bl4ckb0ne>
point is the tip of the index
<pq>
so what you actually want is to group multiple "simple" events into a single update? Construct an update package from whichever events are necessary at a time. Right?
<bl4ckb0ne>
yes
paulk-ter has joined #wayland
ybogdano has joined #wayland
<pq>
many interfaces do thatm often with a "done" or "frame" event that signals the boundary between updates - the end of one update.
<pq>
or even wl_surface.commit in the opposite direction
<pq>
once you have boundary events in the base interface, you can even add extension interfaces into the same mix
<bl4ckb0ne>
what do you mean
<pq>
e.g. like wl_output.done and then extended with.. umm
<pq>
I think there were extension to that
<emersion>
xdg_output stuff
<pq>
or xdg_surface.configure is the boundary event, and then xdg_toplevel and xdg_popup add their own configure stuff on top
<pq>
wl_surface.commit is the boundary request, and then wl_subsurface and xdg_toplevel and what not hook into that.
<bl4ckb0ne>
so each gesture would be its own interface that the compositor sends after a defined boundary event
sav10 has joined #wayland
<pq>
no, unless you have a reason to
<pq>
this is just a way to extend later if something new or different comes up, but basic interfaces needs to be prepared for that
<pq>
you should plan on how to add e.g. new gestures or new pieces of data in the future, things you do not know you need right now
<pq>
do you add new requests and events and bump the interface version, or do you need a more complicated design
<pq>
but at first, you can just forget all that to get the first draft done
<pq>
something like this might work, events: hand_state(netural/fist/point/pinch), position(vec3), orientation(vec4), frame
<pq>
then you can say that hand_state determines how the others must be interpreted
<pq>
and "frame" ties multiple events into a single update
<pq>
up/down/motion I didn't quite understand
<pq>
motion could be use a new position+frame
<pq>
of course, this kind of design relies on the spec documentation to forbid illegal combinations, it doesn't make them impossible
<pq>
that's a trade-off in practicality
<pq>
I wouldn't use e.g. compositor-created objects, nor anything where the client must react before further events can be sent.
devilhorns has quit []
<bl4ckb0ne>
would hand_state be sent each update, or each time it changes?
<bl4ckb0ne>
i havent though about using a frame event, but it makes sense with openxr, there's mark for the beginning and the end of a frame
<bl4ckb0ne>
but i think the xr frame is at a much higher speed than wayland process events
<emersion>
the frame events aren't related to frames presented to the use
<emersion>
they are just a way to indicate the end of a sequence of evens
<emersion>
"you've received all info about the gesture"
<emersion>
*to the user
<bl4ckb0ne>
i see
kts has quit [Quit: Leaving]
<bl4ckb0ne>
thanks for the help pq
<bl4ckb0ne>
ill send both protocols to the mailing list or the wayland-protocol when ill be happy with them, maybe it could interest a few xr compositors
Szadek has quit [Quit: WeeChat 3.7.1]
Szadek has joined #wayland
julio7359 has joined #wayland
paulk has joined #wayland
paulk-ter has quit [Read error: Connection reset by peer]
Leopold_ has quit [Remote host closed the connection]
Leopold_ has joined #wayland
julio7359 has quit [Ping timeout: 480 seconds]
zvarde198830320 has joined #wayland
zvarde19883032 has quit [Ping timeout: 480 seconds]
julio7359 has joined #wayland
Szadek has quit [Ping timeout: 480 seconds]
Szadek has joined #wayland
MajorBiscuit has quit [Ping timeout: 480 seconds]
julio7359 has quit [Ping timeout: 480 seconds]
rgallaispou has quit [Read error: Connection reset by peer]
agd5f has quit [Read error: Connection reset by peer]
agd5f has joined #wayland
sozuba has quit [Quit: sozuba]
Szadek has quit [Ping timeout: 480 seconds]
Szadek has joined #wayland
floof58 is now known as Guest2010
floof58 has joined #wayland
Guest2010 has quit [Ping timeout: 480 seconds]
junaid has joined #wayland
rasterman has quit [Quit: Gettin' stinky!]
fmuellner has quit [Ping timeout: 480 seconds]
rv1sr has quit []
rodrgz has joined #wayland
rodrgz has quit []
tzimmermann has quit [Quit: Leaving]
rodrgz has joined #wayland
rodrgz has quit []
mxz has quit [Quit: cya]
mxz has joined #wayland
mvlad has quit [Remote host closed the connection]
sav10 has quit []
dcz_ has quit [Ping timeout: 480 seconds]
agd5f has quit [Remote host closed the connection]