Closed isaacy13 closed 1 month ago
Gave it a shot and it's not as straightforward as I expected. I got to the point where it'd hit the Dart main()
entrypoint and got it to register (via a callback like DesktopMultiWindow).
However, although the window handles were being created, I couldn't see them nor find them in Spy++
I suspect I'm overlooking something related to RegisterWindowClass(...)
or position/sizing of the window or GetModuleHandle(...)
The easiest workaround for my scenario is to just to fork the project and change the window styling, so that's what I'll do for now
Thinking this might be too niche, closing
It'd be cool if desktop_webview_window could become compatible with other Flutter plugins (e.g.: window_manager)
Although this feature request would not automatically make other plugins compatible (since must register new plugins), it'd improve ease of implementation for compatability
In my (shallow) understanding, if the parent window handle (hwnd_) utilized Flutter's engine (like webview_window::FlutterView does), then it'd be possible to register plugins more easily (e.g.: copy paste import line + register plugin line)
Or possibly do a callback situation like desktop_multi_window does, so users don't need to fork and change desktop_webview_window code and the custom code lives in the user's project (flutter_window.cpp)
I intend to try this with Windows soon-ish, opening ticket if y'all think it'd be cool/possible as well for all platforms. Thanks!