The callback's done event does't work in multiple-thread mode. about wayland-rs HOT 5 CLOSED

Hmm, this is difficult to say with such a small amount of code, as it would depend a lot on what's done around. Do you have a minimal example that can be run and reproduces this issue, including the event-loop setup?

For the matter, calling callback.done directly forwards the API call to the wayland C lib, which is supposed to handle it properly. Does the event appear in the trace if you run your server with the WAYLAND_DEBUG=1 environment variable?

from wayland-rs.

https://github.com/fangyuanziti/wayland-http

All my code placed in this repository. It's a simple compositor with a http API.

Start server

WAYLAND_DEBUG=1 cargo run

Test with a client

WAYLAND_DEBUG=1 weston-simple-damage

The frame function is placed in src/surface.rs.

from wayland-rs.

Okay, I understand your issue.

Using EventLoop::run(), your compositor blocks waiting for events coming from the client before processing things further, including flushing your events to the client. And the two processes deadlock each other. You can observe this is you start two instances of weston-simple-damage for example, the two clients will generate enough events to make your events loop always make progress.

In your case, as you're not guaranteed to have a regular stream of events causing your event loop to progress forward, you should probably use a more explicit handling, like this:

loop  {
    // wait for client events for at most 50 miliseconds
    event_loop.dispatch(Some(50)).unwrap();
    display.flush_clients();
}

from wayland-rs.

EventLoop::run() should be better document to reflect this.

from wayland-rs.

You are right. I will change my main loop code. Thanks for your work 😄

from wayland-rs.