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
Right now, there are a few places where we call UnityUtils methods, mainly calibration components.
It is preferable to use ViewerService (which wraps those methods and then provides an API to call them) instead.
Suggested solution
Invoke the equivalent UnityUtils methods from ViewerService instead. If missing, create them.
Goal
Avoid using UnityUtils directly from components outside the Viewer
Tasks
Identify the places (outside the ViewerService) where UnityUtils methods are invoked
If missing, create the wrapper for those methods in ViewerService (note: I use the word "wrapper", but they might be more than mere wrapper. For instance, instead of just awaiting for the viewer to be ready and then call the UnityUtils method, they may contain more logic to provide a more concise API that better reflects the frontend needs. Use discretion)
Replace those UnityUtils methods with ViewerService methods
The text was updated successfully, but these errors were encountered:
Description
Right now, there are a few places where we call
UnityUtils
methods, mainly calibration components.It is preferable to use ViewerService (which wraps those methods and then provides an API to call them) instead.
Suggested solution
Invoke the equivalent UnityUtils methods from ViewerService instead. If missing, create them.
Goal
Tasks
The text was updated successfully, but these errors were encountered: