Replies: 1 comment
-
I'll close this in favour of #4344 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone! I am writing an engine with support for hot reloading using DLLs, but I am having problems with calling Window functions over the DLL boundary.
The main structure of my project is.
When running in release mode, the callback trait is created on the main thread. When running in hot_reload mode a wrapper is used that loads the callback code from a DLL. In release mode everything works as expected. However, in the hot_reload mode the Window functions are not found (on MACOS).
I know window functions must be called from the main thread in MACOS. But how does it work across DLL boundaries, isnt it still being called from the main thread? Any help would be very appreciated.
One solution would be to cache the relevant data in the core engine. However, I want to use crates such as egui which need to call these window methods directly.
I have had problems with logging since its a static variable that gets different values for different compilation units, could this be similar to that problem?
Beta Was this translation helpful? Give feedback.
All reactions