Welcome to tomaka/glutin, the official gitter channel for Glutin and Winit! - Github: https://github.com/rust-windowing/glutin, https://github.com/rust-windowing/winit - Crates.io: https://crates.io/crates/glutin, https://crates.io/crates/winit - Docs: https://docs.rs/glutin/0.21.0/glutin, https://docs.rs/winit/0.20.0/winit/
maroider: idk how winit works wrt reviewing, is there any chance of rust-windowing/winit#2025 getting in before the 0.26 release?
1 reply
👋 I'm trying to build the wgpu "just open a window" example from here: https://sotrh.github.io/learn-wgpu/beginner/tutorial1-window/
But when I run it, no window actually appears. It doesn't crash, and I do see it in the list of applications running. Just no window
3 replies
I suspect this is because I'm using Wayland via EGLStreams (thanks NVIDIA), and I understand Wayland is enabled by default for winit. Can I force winit to use X11 (and thus go via XWayland) somehow to see if that helps matters?
1 reply
but the PR seems fairly simple, so it shouldn't be too hard to get it merged in practice
no, it's not wrong per se
if proceeding to the next part of the tutorial doesn't work, then you can assume something is wrong
All this does is create a window, and keep it open until user closes it, or presses escape. Next tutorial we'll actually start using wgpu!
I mean, is this part wrong?
cwfitzgerald: I'll see if I can't take a look at it in the next couple of days. I have IRL stuff that urgently needs doing, but I think I can put aside enough time for this.
1 reply
No real urgency on this, just would like to get it on for 0.26 as using grab is currently broken without it
And it also looks like GNOME Screenshot spares you winit's beautiful CSD
IIRC, winit is going to lose its built-in CSD in the next release, so I suppose the screenshot accurately represents the near future for GNOME users
1 reply
any built-in CSD support has been removed, and I don't know if or when libdecor support might be added
1 reply
winit's current Wayland maintainer doesn't seem to want to work around GNOME being "special" and not supporting server-side decorations, and idk how prioritized the issue is upstream (ie. in
smithay-client-toolkit, which is where winit used to get the CSD from).
1 reply
Also, libdecor support is pretty high on the toto-list of SCTK. However, it is a hobby project done by a single person, so the bottleneck is time that can be allocated to it.
it's a bug that winit is emitting LoopDestroyed Events at the end of each call to run_return on macOS, right
or is that expected behavior and yet another reason not to use run_return
what just happened?
ngl
maybe it's time to finally move to a new room and bridge to a new IRC channel
(for those lacking the context: the only person with admin privileges in this room is unresponsive)
1 reply
Well I'll be waiting for the new bridge then
I think I've figured out the right way to set up a bridge, but it keeps timing out on me :(
I have tried the element.io web app, in both firefox an chromium, and I've tried element-desktop and the mobile app
all of them fail at various points
I don't think I'm getting this done today 😓
Over at smithay we appear to be using @appservice:libera.chat for the bridge?
I've asked in their "matrix bridge help channel", but this looks like a bit like a client-side bug
or rather: multiple client-side bugs