-
Notifications
You must be signed in to change notification settings - Fork 121
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
basic winit port #176
basic winit port #176
Conversation
This is much cleaner than I would have expected. Overall LGTM and I’m comfortable merging now and making further changes incrementally. |
It's not really clean, because there are a bunch of hanging references in |
What do you mean exactly? |
I mean that the |
I skimmed the PR and tested it. It works for me (tested on mac), and further work blocks on it. My preference is to merge soon, and document all the regressions and rough edges to those can be separate PRs. Thanks for the work! |
Yeah. I'll add the removals for the the features that are broken by this PR and pull it out of draft; we can go-no-go at the Office Hours tomorrow. |
I'm running into a weird issue at this line (so far I could pinpoint it at least): Line 231 in 623f18a
This seems to deadlock for me with this PR, after a few frames painted (slightly under 10 frames). I'm not sure where the exact issue could be. I'm testing on Hyprland (wayland + nvidia beta driver) currently. I can try on X11 if it works there for me. I just tried the wgpu raytracing triangle example which works for me (maybe relevant). |
I just tested it on X11, there it works. I can still provoke the Outdated swapchain texture issue though when resizing... |
Ok, I'm pretty sure it's a wgpu issue, I could reproduce the issue with the examples on wgpu 0.18 (which is what xilem still uses). But not on wgpu 0.19 |
Ok, no unfortunately it wasn't as easy as that... Same issue though, deadlock at that line after some frames... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I could "fix" it by commenting out these two lines: https://github.com/gfx-rs/wgpu/blob/b8a8ff6e44162a41b8d54184a88613794dd3d2e4/wgpu-hal/src/vulkan/instance.rs#L967
And since these lines don't exist on the trunk
branch on wgpu, it does work indeed with
[patch.crates-io]
wgpu = { git = 'https://github.com/gfx-rs/wgpu.git' }
in Cargo.toml
(after updating/adjusting wgpu and vello in xilem).
When no one else has these issues (seems to happen on wayland + vulkan + maybe nvidia), I'd be ok to merge with this regression, as it otherwise looks good to me.
Maybe it also makes sense to add the lines above to Cargo.toml
(but I guess this can be its own PR on top of this, including the update to wgpu and vello).
FWIW, here's my changes to get that working for me with wayland: Philipp-M@9ab5c83 |
When this is merged, please put that up as a PR. :+ ) |
This removes (for now) accessibility, as well as the system menu.