Run a ComponentHandle from a pre-initialized "WindowAdapter"

[Starz0r]

If I want to run a component as a Window today, I have to do this:

slint::slint!{
	export component Foo inherits Window {
	}
}
pub fn main() -> Result<(), dyn Box<Error + Send + Sync + 'static>> {
	Foo::new()?.run()?;
	Ok(())
}

This of course, automatically handles creating a window behind the scenes for me. Perhaps, instead, I would like to do this myself by hand, but, cannot as there is no way to pass such a parameter. What I'm asking for is to perhaps be able to initialize the window myself, then pass the handle to the component to be used and inhabited by the component I'm running. Using winit, I'd be able to do something like this maybe:

slint::slint!{
	export component Foo inherits Window {
	}
}
pub fn main() ->Result<(), dyn Box<Error + Send + Sync + 'static>> {
	let ev_loop = winit::event_loop::EventLoop::new()?;
	let wnd = ev_loop.create_window(...)?;
	Foo::from_window(ev_loop, wnd)?.run()?;
	Ok(())
}

Does this sound reasonable? This doesn't take into account alternative backends like Qt, but for my use case, I only need the default, standard backend. It also might be more involved depending on whether creating windows for other "renderers" is any different than creating one from winit.

[tronical]

Generally this sounds reasonable. Perhaps the winit backend‘s api should provide a hook. Could you describe your use-case a little?

(note that with the next winit release create_window() can’t be called like that anymore, only on an active event loop after receiving can_create_surfaces())

[Starz0r]

Could you describe your use-case a little?

The idea is that I might need to let another program or library inhabit the window first. By initializing the window by hand I can pass it to the library so it can draw on it, then pass it to Slint to then draw over that.

If this is reasonable, should I open an issue or is a discussion post enough?