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
Company has quit [Quit: Leaving]
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
nerdopolis has quit [Ping timeout: 480 seconds]
cabal704 has quit [Quit: WeeChat 3.5]
Brainium has quit [Quit: Konversation terminated!]
cool110 has quit [Remote host closed the connection]
chipxxx has quit [Remote host closed the connection]
fahien has joined #wayland
cabal704 has joined #wayland
nerdopolis has joined #wayland
chipxxx has joined #wayland
cabal705 has joined #wayland
cabal704 has quit [Ping timeout: 480 seconds]
rv1sr has joined #wayland
chipxxx has quit [Read error: No route to host]
<mvlad>
emersion, we currently have a couple of incoming fixes for 11. And just I saw a bisect pointing to a potential commit from 10.91 (some revert we did a while back wrt to atomic pointer updates hehe). We would like to have another RC this week. Well, at the end of the week (to see if we can track the atommic cursor stuff). And with it to postpone the release for next week, instead of having it doing it tomorrow (from 13 of Sept to
<mvlad>
19).
<emersion>
mvlad: ack, would it be fine to do RC tomorrow, and potential final next week?
<emersion>
to not move the schedule
<mvlad>
emersion, ah, would've like to include a potential fix that atomic cursor part, but IDK if we can fix it until (and include in the that RC).
<emersion>
hm
<emersion>
how about this: i send an ANNOUNCE saying that an RC will be released on Thursday (not Friday because releasing on Fridays is a good recipe for mistakes)
<mvlad>
so I have two incoming fixes which I'll land today, but there's one more that romangg added.
<mvlad>
emersion, yeah sounds good to me. ManMower ^^
<emersion>
then we release RC2 on Thursday, and then tentative final for Thursday next week
<mvlad>
emersion, uhum, yup.
<daniels>
grrr cursors
<daniels>
+1w sounds good tho
<daniels>
thanks :)
<kchibisov>
If I issue text_input::set_cursor_rectangle() and then commit(). Must compositor reply to me with `done` and `preedit`, ect?
<kchibisov>
I was told by some IME writers that on `commit` compositor will reply with the current state back which in my case causes infinite loop between the compositor and client.
<kchibisov>
And just by reading text_input_v3 I don't get that this could even happen and is desired behavior for send IME position only when it changes and not on each redraw.
<kchibisov>
Also, if I change surface state, like resize it, does it invalidate the position I've set for IME popup from set_cursor_rectangle?
devilhorns has quit [Remote host closed the connection]
conplan has quit [Remote host closed the connection]
mvlad has quit [Remote host closed the connection]
thevar1able1 has quit []
thevar1able has joined #wayland
mbalmer has joined #wayland
rv1sr has quit []
mbalmer has quit []
sozuba has quit [Quit: sozuba]
cool110 has joined #wayland
dcz_ has quit [Ping timeout: 480 seconds]
<bwidawsk>
Is there any history with attempting to port the weston tests to another compositor? Do we already know what failed and/or is hard?
<emersion>
Mir has a test suite capable of running with multiple compositors
<emersion>
the hard part is that it requires at least some compositor integration
<i509VCB>
We use wlcs (mir's test suite) in Anvil (smithay's duck tape driven development compositor) and it works well enough. Although we haven't turned on all the tests yet
<i509VCB>
Compositor integration actually makes sense when you look at how testing in wlcs works (test clients that do wrong things and possibly wlcs driven moves and resizes)
<Lightsword>
anyone know how to change the buffer size passed in zwp_linux_buffer_params_v1@15.create_immed(new id wl_buffer@16, 1024, 768, 875713089, 0)?
<i509VCB>
As in request a different size or create a larger buffer?