Emil Ernerfeldt
Emil Ernerfeldt
That sounds like a good idea! Would you like to contribute it?
I think a separate folder is better first step (easier to keep up-to-date). If it works well, we can maybe switch it to be the default :)
This is a really great feature to implement, but I wonder if we can make it more ergonomic. ---- Let's investigate the current approach first (3.). Every user must add...
Blocked on: * https://github.com/gfx-rs/wgpu/pull/2918
A new wgpu release isn’t due until late September, so either we wait until then or we make egui-winit compatible with both old and new winit, with a feature-flag to...
> I might have a solution to this: [rust-windowing/winit#2418](https://github.com/rust-windowing/winit/pull/2418) > > So this way Winit would implement the old and new `raw_window_handle` traits which can hopefully make Winit 0.27 compatible...
The only way to support this is if you know the heights of the elements beforehand. For instance, if you are showing a bunch of images of different sizes, you...
@xNxExOx: some things should probably be made `pub`. Open a PR …but also: containers, such as scroll areas, are not always easy to implement in egui :)
Oops, yes it seems `content_is_too_small` is named the opposite of what it means 🤦. Will fix
Related issue: https://github.com/emilk/egui/issues/427 This is a limitation from `winit`, so I suggest you open a `winit` issue on this: https://docs.rs/winit/latest/winit/event_loop/struct.EventLoop.html#method.run You can use another backend (e.g. [`egui-macroquad`](https://crates.io/crates/egui-macroquad)) if this is...