Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Have Compositor::build_{auto,headless,x11,wayland,drm} actually start the backend #274

Open
Timidger opened this issue Feb 17, 2019 · 0 comments
Labels
Breaking Breaking changes

Comments

@Timidger
Copy link
Member

Currently we are deferring it to the run method. I'm not sure why we are doing that, but it probably isn't necessary to do this especially because there might be race conditions if we acquire those resources late in compositor startup code.

If it shouldn't be done there then we should make another affine type that the Compositor builds out to that can enforce manually trying to start the backend only once. (this will mess with the naming a bit, ultimately the final type should be Compositor so we might want to rename the output of the builder methods).

@Timidger Timidger added the Breaking Breaking changes label Feb 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Breaking Breaking changes
Development

No branches or pull requests

1 participant