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
leon-p has joined #wayland
leon-p_ has quit [Ping timeout: 480 seconds]
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
floof58 has quit [Ping timeout: 480 seconds]
floof58 has joined #wayland
boistordu has joined #wayland
boistordu_ex has quit [Ping timeout: 480 seconds]
bgs has quit [Ping timeout: 480 seconds]
bgs has joined #wayland
txtsd has quit [Ping timeout: 480 seconds]
| has joined #wayland
| has quit []
| has joined #wayland
leon-p has quit []
zebrag has quit [Remote host closed the connection]
slattann has joined #wayland
dcz has joined #wayland
dcz_ has joined #wayland
dcz has quit [Ping timeout: 480 seconds]
slattann has quit []
slattann has joined #wayland
alan_ has joined #wayland
jgrulich has joined #wayland
pnowack has joined #wayland
hardening has joined #wayland
<zubzub>
21:05 < daniels> zubzub: you could help review some of the extant MRs which fix a bunch of bugs
<zubzub>
21:05 < daniels> but what do you mean by 'improved'
<zubzub>
I can test them but I'm not sure how qualified I am in reviewing them :)
<zubzub>
daniels: improve as in make sure a lot of X applications work, ie it seems that java apps (jetbrains ides at least) are currently broken on Xwayland on Weeston
<zubzub>
my X fu is not strong enough to quickly fix it, although I can probably pinpoint why it's not doing what it's supposed to do
<zubzub>
context:
<zubzub>
10:13 < zubzub> How well is weston Xwayland support? I'm asking because jetbrains ides are completely broken on Weston 9. Since I'm basing my own XWayland integration on Weston, I have the same issues. (but I
<zubzub>
guess that means I c/p Weston's implementation well...)
danvet has joined #wayland
<kennylevinsen>
Is it just the autocorrect popup making things broken? If so, that's just one bug regarding really annoying focus behavior
<zubzub>
also application menus
<zubzub>
on startup the screen is also blank until a resize triggers a redraw
<kennylevinsen>
Menus are possibly the same. Not sure about the last one. IntelliJ is notoriously quirky though, quite an outlier...
bluebugs has quit [Remote host closed the connection]
floof58 has joined #wayland
rasterman has quit [Quit: Gettin' stinky!]
cedric has joined #wayland
spstarr has quit [Remote host closed the connection]
cedric is now known as bluebugs
codecolla has joined #wayland
zebrag has joined #wayland
<codecolla>
Hi all, I was shure to see a way to recieve form server an event notifying client that refresh just happen and that's the best time to redraw surfaces
<codecolla>
Did I dream or can I put a callback on a such event?
<emersion>
wl_surface.frame is a good time to redraw
<codecolla>
Thanks, I'll surely still need help, but for the moment I read doc before asking more questions.
<codecolla>
When I see wl_surface::frame - request a frame throttling hint , callback id of the callback, etc...
<codecolla>
I have to struct wl_callback *callback = wl_surface_frame(surface);
danvet has quit [Ping timeout: 480 seconds]
<codecolla>
But when I have wl_surface::damage - mark part of the surface damaged, x int - surface-local x coordinate, y, etc...
<codecolla>
I have to wl_surface_damage (window->surface, 0, 0, window->width, window->height);
<codecolla>
How to know when doc mentions that what is listed under "method" is either an arg or a return value?
d_ed has joined #wayland
<emersion>
new_id is a return value
<codecolla>
Ok so wl_shm::create_pool is written struct wl_shm_pool = wl_shm_create_pool(int fd, int size); do I understand it right?
___nick___ has quit [Ping timeout: 480 seconds]
<codecolla>
Ha no, wl_shm_pool = wl_shm_create_pool(struct *wl_shm, int fd, int size); isn't it?
<daniels>
right
<daniels>
every request always takes the interface it's part of as the first part of the arg
<daniels>
so wl_surface_*() will always take a wl_surface as the first param
<daniels>
otherwise you don't know what you're calling it on
<codecolla>
Ok, that makes sense
<codecolla>
Sorry I've a lot of question, I'm discovering wayland...
<codecolla>
And the last one do I really need to register a frame callback every time I draw. Can't I just register it once for all?
<kennylevinsen>
No, it's one-shot which is intentional: you render when you have something new to show and register a frame callback. On the callback, if you more stuff you do it all again - otherwise you do nothing and stop recieving events
<kennylevinsen>
Continuous vsync events lead to bad designs where all often unrelated sorts of stuff ends up relying on a constant vsync timer, and often wastes resources.
<emersion>
also a client lagging behind would get its receive buffer fill up
<codecolla>
Ok, that still fit my needs and I guess, the needs of every wayland users...
<kennylevinsen>
You also only get the event if the compositor wants you to render - not when hidden for example
<codecolla>
If I have continuous annimation to perform, I don't know what other design would I implement...
<kennylevinsen>
Ask for the frame callback as long as the animation is going
<codecolla>
Yes, I render each vsync, but not more, and if window hidden, not perform any animations by this time seems good for me.
<codecolla>
That leads to another question : what if my surface is hidden by another transparent one, will composer still notify me for frame refresh?
<kennylevinsen>
It's not hidden if it's visible
<codecolla>
Ok composer states that an even partially transparent pixel makes underlaying window visible, isn't it?
ohaiyo has quit [Ping timeout: 480 seconds]
<codecolla>
Ok, thanks for all and see you.
codecolla has quit [Quit: Leaving]
rasterman has joined #wayland
leon-p_ has joined #wayland
hardening has quit [Ping timeout: 480 seconds]
leon-p has quit [Ping timeout: 480 seconds]
Seirdy has quit [Quit: exiting 3.2]
<wlb>
wayland.freedesktop.org/main: Peter Hutterer * libinput: add the missing API documentation for 1.19 https://gitlab.freedesktop.org/wayland/wayland.freedesktop.org/commit/5568bbf922b4 libinput/doc/1.19.0/api/ annotated.html bc_s.png bdwn.png bug.html classes.html closed.png deprecated.html dir_cfbb6e647ca2f051430f2185dea647d3.html dir_e68e8157741866f444e17edd764ebbae.html doc.png dot_inline_dotgraph_1.png doxygen.css dox