Solver Handler Transform Synchonization

[StephenHodgson]

Overview

Example of solver handler implementation using IMixedRealityControllerPoseSynchronizer

Fixes: #2785

(I only added a solver handler to the parabolic pointer as trying 2018.3 may have temporarily broke prefab editing for me)

[keveleigh]

Is this solution is to put a ControllerPoseSynchronizer on every solver?

[StephenHodgson]

Is this solution is to put a ControllerPoseSynchronizer on every solver?

No, this doesn't make that a requirement

[keveleigh]

But to track controllers, it is?

[StephenHodgson]

But to track controllers, it is?

Not the concrete type, but the IMixedRealityControllerPoseSynchronizer, yes. or else how would you get any data about any controller?

[keveleigh]

Using a controller pose synchronizer for every solver that needs to track a controller does not fulfill the acceptance criteria for #2785 of

Doesn't add another global listener to the scene

[StephenHodgson]

Doesn't add another global listener to the scene

It doesn't. It's using the ones we're already using.

This definitely fulfills those requirements.

[keveleigh]

It's using the ones we're already using.

If I create a new prefab that adds a cube tracking the front of my right controller via solver, I will not need to add a new controller pose synchronizer to it?

[StephenHodgson]

Nope, not as long as you get your right controller's IMixedRealityControllerPoseSynchronizer reference

[keveleigh]

Where can I get that reference?

[StephenHodgson]

It gets it for you, if the handler is already attached to a game object that has a IMixedRealityControllerPoseSynchronizer

[StephenHodgson]

Please feel free to take this and change it up to better fit what your needs are, open a PR on my branch, or open a new PR with your own take, that tries to synchronize the pose in this way.

[keveleigh]

To clarify, back to my scenario a few comments up, if I have a brand new cube prefab and I add a solver to it, where do I get an existing reference to a pose synchronizer?

[Ecnassianer]

I'm not very familiar with expression-bodied members, but doesn't this remove the setter? SolverHandlers need a public setter so they can be set to follow non-tracker objects (e.g, any random game object) at runtime.

[StephenHodgson]

You can still set any transform to track, this is just a read only value of the currently tracked transform's type.

[Ecnassianer]

Ah, right. "secondTransformOverride" didn't show up in the diff, so I got the two mixed up.

But I guess that prompts a similar question. If this becomes read only, how does gameplay logic tell the solver to start tracking a motion controller again? It has to find the proper motion controller in the scene and override the TransformTarget? That seems like an undesirable complication.

[StephenHodgson]

I can see how that would be useful.

[StephenHodgson]

Added a DNM as this is just an example.