Support the new Unity Input System

[rblenkinsopp]

Summary

This ensures that all the parts of the main Ultraleap Tracking package support the new Unity Input System.

Only the UIInputModule in the Tracking Preview package and the controller example for the input manager does not work with this system. These have been split into a set of examples for the input manager (old) from the existing tracking preview examples which are now the main examples. There is also a common set of example assets that need to be imported for both example 'packages' to work.

While splitting/moving the examples, a couple of issue have been fixed with the UI input scene

1. The indirect click has been fixed.
2. The toggle button text now finally toggles with the toggle state to on/off!

Contributor Tasks

• Create or edit test cases here
• Add a CHANGELOG entry for this change.
• Ensure documentation requirements are met e.g., public API is commented.
• Consider any licensing/other legal implications for this MR e.g. notices required by any new libraries.

Test Cycle

Link to the test cycle here.

Reviewer Tasks

• Code reviewed.
• Non-code assets e.g. Unity assets/scenes reviewed.
• All tests must be ran and cover all scenarios (If not, add new tests to the cycle and run them).
• Documentation has been reviewed.
• Approve with a comment of any additional tests run or any observations.

Related JIRA Issues

If this MR closes any JIRA issues list them below in the form Closes PROJECT-#

Pull Request Templates

Switch template by going to preview and clicking the link - note it will not work if you've made any changes to the description.

• default.md - for contributions to stable packages.
• release.md - for release merge requests.

You are currently using: default.md

Note: these links work by overwriting query parameters of the current url. If the current url contains any you may want to amend the url with &template=name.md instead of using the link. See query parameter docs for more information.

[MaxPalmer-UH]

Just tried pulling that branch and then using the physical hands example scene. Using Unity 2022.3 and a clean project with the XT Template. I see this (see below). Perhaps some of our samples are set up not to use the new input system?

[MaxPalmer-UH]

[rblenkinsopp]

Just tried pulling that branch and then using the physical hands example scene. Using Unity 2022.3 and a clean project with the XT Template. I see this (see below). Perhaps some of our samples are set up not to use the new input system?

That's possible, I was ensuring that all the places where the old input system was used also had pathways for the new input system in parallel. I'll pull that example and take a look.

[MaxPalmer-UH]

Ah, looks like we need to go through the samples and search for EventSystem, then hit this button? (Yes, that clears out the warnings)

[MaxPalmer-UH]

[rblenkinsopp]

Ah OK, then yes we should update the samples by default to the new system I think?

[MaxPalmer-UH]

Yes, I think so.

[rblenkinsopp]

I double-checked the code regarding the two versions of the tracked pose driver, it already handles both of those cases correctly. However, we may also want to convert the samples to use the new Tracked Pose Driver (Input System) version rather than the legacy one.

[rblenkinsopp]

I've rebased this now to avoid a duplication of all the copyright changes.

[rblenkinsopp]

I fixed a few errors that I noticed during review with the preview package's import all examples script. I had to rename the samples to match the folders to get consistent behaviour again (other wise it gets imported with the display name which isn't very helpful), it was also missing an import to the base examples package for the SampleDependencyImporter.

[rblenkinsopp]

What other changes did you make to the scene files, as at first glance they are still using "Input Pose Driver"?