Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor Solver System to be more extendible and user friendly #10759

Closed
RogPodge opened this issue Jul 18, 2022 · 3 comments
Closed

Refactor Solver System to be more extendible and user friendly #10759

RogPodge opened this issue Jul 18, 2022 · 3 comments

Comments

@RogPodge
Copy link
Contributor

RogPodge commented Jul 18, 2022

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.

@keveleigh
Copy link
Contributor

Previously discussed in #2798 and #4675 as well.

@SimonDarksideJ
Copy link
Contributor

Ahh, this brings back such memories @keveleigh and for beating me to referencing that age old request :D

@AMollis
Copy link
Member

AMollis commented Mar 10, 2023

Related PR #11323

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants