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/
kchibisov on Freenode Like the amount of GNOME bugs I've seen is rediculuos.
UndeadLeech on Freenode We should be aware of how the application behaves. If something cannot be tested on GNOME then that should be stated ahead of time.
kchibisov on Freenode And it's not that hard to trigger them.
UndeadLeech on Freenode If there is a GNOME bug, we should be aware of it.
kchibisov on Freenode I mean, I report them to GNOME sometimes.
kchibisov on Freenode Like HiDPI on GNOME is completely broken last time I've tried.
UndeadLeech on Freenode So?
kchibisov on Freenode nothing, I guess.
Kai Mast Just tested the bugfix and it resolves the problem for me.
kchibisov on Freenode Kai Mast: yeah, just set min_inner_size if you really want it on a window and not in a builder.
UndeadLeech on Freenode If something applies only to certain compositors, that should be made clear from the start. If it should work on all compositors and it turns out during the testing process that it doesn't, that's exactly what testing is there for.
kchibisov on Freenode I mean the thing with GNOME that it can arbitrary downscale you.
kchibisov on Freenode So I can't just state in every PR, 'please don't test anything on GNOME with HiDPI or verify logs in WAYLAND_DEBUG=1'.
kchibisov on Freenode I mean I agree that everything should be tested, I just don't want to test GNOME bugs.
Kai Mast (I think since 0.23 most issues have been resolved for me though)
kchibisov on Freenode I mean, I test sway, gnome, weston, and sometimes KDE.
kchibisov on Freenode But if you really want to test things you can add yourself as a tester on Wayland.
kchibisov on Freenode https://github.com/rust-windowing/winit/wiki/Testers-and-Contributors
kchibisov on Freenode Into this table ^
UndeadLeech on Freenode Why are you creating a window with a different library?
fuzbuz on Freenode If I can somehow convert the raw handle into a winit window, then it fits into the ecosystem nicely. If not, I suppose I can work around it.
UndeadLeech on Freenode Which library gives you that window handle?
fuzbuz on Freenode I'm 95% sure it's coming from Qt
UndeadLeech on Freenode Shouldn't you use Qt then?
fuzbuz on Freenode Nope. For multiple reasons: I really dislike Qt, I'd rather work in Rust, and the rendering library is already written in Rust and I don't feel any need to rewrite it just to satisfy a single use of the library.
UndeadLeech on Freenode If you really dislike Qt, why are you letting it create windows for you?
fuzbuz on Freenode I'm not. Someone else is and then giving me the window handle.
UndeadLeech on Freenode Are you being held hostage?
fuzbuz on Freenode In the literal sense, no. I do like keeping my boss happy, though.
UndeadLeech on Freenode What exactly do you want winit to do for you?
fuzbuz on Freenode At some point the rendering code has to turn it back into a raw handle for OS reasons, I can just add a function that passes an already-raw-handle down to that level.
fuzbuz on Freenode But it would be nice if I didn't have to do that.
UndeadLeech on Freenode Is that a crate, or did you write the rendering library yourself? Fundamentally taking just a winit window for rendering doesn't make a ton of sense.
UndeadLeech on Freenode Winit's purpose is to manage your windows and window events. If you don't have winit manage your windows, there's little point in using it.
fuzbuz on Freenode I have a rendering crate that is used in several Rust-only projects. The rendering crate takes a winit Window to provide the rendering context as the Rust-only projects use winit for managing the windows and window events. A new project, mostly in C++, wants to also use the rendering code and can provide me with a raw window handle.
fuzbuz on Freenode As I'm making the C FFI interface for the rendering crate, I need to either turn that raw handle into a winit Window or I need to make changes to the rendering to allow using raw handles. The former is cleaner but the latter isn't a problem.
fuzbuz on Freenode I'm just curious if there is a way to do the former that I am failing to discover by reading the docs
UndeadLeech on Freenode Which should be documented in winit's documentation.