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 Jul 10, 2023. It is now read-only.
Currently the API has no concept of the "main thread" of an application, and assumes that VRServiceManager::new() and VRServiceManager::register_defaults() can be safely called from any thread (in servo, they're called from the WebVRThread). This has a mismatch with devices (such as MagicLeap) which have a main thread, and where the APIs to access the device capabilities aren't thread-safe.
The text was updated successfully, but these errors were encountered:
asajeffrey
changed the title
Supporting devices that require initialization on the main thread
Supporting devices that require code to run on the main thread
Feb 25, 2019
Add glwindow implementation, that renders to a GlWindow
Add glwindow implementation, that renders to a GlWindow, mainly for testing, but also this forms a basis for VRDisplays that have code that needs to run in the main thread.
Fixes#52 and #65.
Currently the API has no concept of the "main thread" of an application, and assumes that
VRServiceManager::new()
andVRServiceManager::register_defaults()
can be safely called from any thread (in servo, they're called from theWebVRThread
). This has a mismatch with devices (such as MagicLeap) which have a main thread, and where the APIs to access the device capabilities aren't thread-safe.The text was updated successfully, but these errors were encountered: