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

Add an owned display handle type #3365

Closed
notgull opened this issue Jan 5, 2024 · 3 comments · Fixed by #3395
Closed

Add an owned display handle type #3365

notgull opened this issue Jan 5, 2024 · 3 comments · Fixed by #3395
Labels
D - easy Likely easier than most tasks here P - normal Great to have S - enhancement Wouldn't this be the coolest?

Comments

@notgull
Copy link
Member

notgull commented Jan 5, 2024

It would be nice if there was an owned display handle that implemented HasDisplayHandle independent of EventLoop or EventLoopWindowTarget. It could keep this display alive.

It would be useful for glutin and potentially wgpu

@notgull notgull added D - easy Likely easier than most tasks here P - normal Great to have S - enhancement Wouldn't this be the coolest? labels Jan 5, 2024
@daxpedda
Copy link
Member

daxpedda commented Jan 6, 2024

Isn't this the same as #3317?

@notgull
Copy link
Member Author

notgull commented Jan 6, 2024

No, for graphics ecosystem cases a persistent display handle is necessary.

@daxpedda
Copy link
Member

daxpedda commented Jan 6, 2024

Ah, sorry, display vs window.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
D - easy Likely easier than most tasks here P - normal Great to have S - enhancement Wouldn't this be the coolest?
Development

Successfully merging a pull request may close this issue.

3 participants