How to map eframe/egui window events to three-d?

[GBagley]

I'm using three-d with eframe and egui (using a window that they create), and trying to map mouse events to a three_d::renderer::control

Previously, I had been getting the events from an egui::InputState (and egui::Event), and then translating those into three_d::renderer::control::Event, but the latest version of three_d has changed to using this LogicalPoint struct which has some private fields, so I don't think I can construct the three-d events myself now:
https://docs.rs/three-d/latest/src/three_d/renderer/control.rs.html#33-34

It seems the right way to do this is to use a three_d::window::FrameInputGenerator, and pass it a winit::Window

Question is; how the heck do I get the winit::Window that eframe and/or egui has created for me? I'm sure this must be possible and I'm just not seeing it.

[asny]

Previously, I had been getting the events from an egui::InputState (and egui::Event), and then translating those into three_d::renderer::control::Event

Makes sense! It was necessary to manually map the events before which is quite a lot of code, so I hoped introducing the FrameInputGenerator would make it simpler, but maybe not 😬

the latest version of three_d has changed to using this LogicalPoint struct which has some private fields

Maybe that's unfortunate that you can't create a LogicalPoint yourself 🤔 I'll definitely consider making a constructor so you can always do it manually.

It seems the right way to do this is to use a three_d::FrameInputGenerator, and pass it a winit::Window

Yes exactly, if you haven't already found it, the winit_window example shows how to use it.

Question is; how the heck do I get the winit::Window that eframe and/or egui has created for me? I'm sure this must be possible and I'm just not seeing it.

That's a good question. It seems to me that eframe WindowBuilder returns the winit window when you call build? And from there, it should be the same as the winit_window example. Actually, I wanted to add an eframe example to three-d, similar to the winit_window example, but haven't had the time yet.

[GBagley]

hmm... it does look like WindowBuilder returns what we want. We're not using that though. We're using the eframe::run_native() to run an app that is managed by eframe, and the window building is done for us by eframe. Similar to the example at the top here: https://docs.rs/eframe/latest/eframe/index.html

In their eframe::NativeOptions that is passed into eframe::run_native, there is an option to supply a window_builder hook, where you can hook into the WindowBuilder, but I don't think I can call build() from there - instead I can only change parameters of the window builder prior to eframe ultimately calling build()

I see that in the eframe::CreationContext that my app gets, there's an option to get a raw_display_handle, which is the result of eframe calling raw_window_handle() on the winit::Window:
https://docs.rs/raw-window-handle/0.5.2/raw_window_handle/trait.HasRawDisplayHandle.html#tymethod.raw_display_handle

I'm not sure that I can turn that back into a winit::Window, or if it's otherwise very useful in this case:
https://docs.rs/raw-window-handle/0.5.2/raw_window_handle/enum.RawDisplayHandle.html

[asny]

This seem like a eframe question more than a three-d question 🤔 I'm not an eframe expert but afaik, eframe is just a thin wrapper around a winit window so I doubt run_native actually does a lot. Maybe look at that code and copy it if it's simple?