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
Basically, Solvers needlessly inherit from Monobehaviors so that they can exist as components on a gameobject, even though they do not perform any independent actions during update. This results in several design quirks, like relying on inspector ordering and having to register and unregister from a SolverHandler.
This issue tracks re-architecting the system to improve on the current design.
The text was updated successfully, but these errors were encountered:
This issue has been migrated a new MRTK repository, and the status of this issue will now be tracked at the following location:
Based on comments left from #10748
Basically, Solvers needlessly inherit from Monobehaviors so that they can exist as components on a gameobject, even though they do not perform any independent actions during update. This results in several design quirks, like relying on inspector ordering and having to register and unregister from a SolverHandler.
This issue tracks re-architecting the system to improve on the current design.
The text was updated successfully, but these errors were encountered: