You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 31, 2025. It is now read-only.
If we can move most devices off the main thread, this just leaves glwindow on macos as being the only device with main thread affinity. We could refactor the code so that the main-thread code is in webxr/glwindow rather than webxr-api which would avoid the complexity on platforms which don't need it.
The text was updated successfully, but these errors were encountered:
Oh, that's an interesting plan. So basically when we set up the discovery object we give it a handle to the main thread for the few cases where it needs one? That can work.
I think we could just rip out all the main-thread-specific code, and for devices that have main thread affinity, they can do the messaging themselves. The downside would be one more active thread for devices which have main thread affinity, but if that's just the glwindow test device then I'm not too worried.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If we can move most devices off the main thread, this just leaves glwindow on macos as being the only device with main thread affinity. We could refactor the code so that the main-thread code is in webxr/glwindow rather than webxr-api which would avoid the complexity on platforms which don't need it.
The text was updated successfully, but these errors were encountered: