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

Investigate if input subsystems can be removed from Core package. #11592

Closed
1 task
AMollis opened this issue May 31, 2023 · 0 comments
Closed
1 task

Investigate if input subsystems can be removed from Core package. #11592

AMollis opened this issue May 31, 2023 · 0 comments

Comments

@AMollis
Copy link
Member

AMollis commented May 31, 2023

This issue has been migrated a new MRTK repository, and the status of this issue will now be tracked at the following location:


Overview

There are some data binding classes in the Core MRTK3 package. Do these need to be in the Core package? Can they be moved to the data binding package? If not moved, these need to be marked as experimental.

Similarly, need to understand why the input subsystems are in the Core MRTK3 package. Can they be moved to the Input package?

Tasks

  • KeywordRecognitionSubsystem, HandsAggregatorSubsystem, HandsSubsystem are in the Core package, but the documentation is under the Input package. Should the implementations be move to the Input package.

Parent Task

@github-actions github-actions bot added the MRTK3 label May 31, 2023
@AMollis AMollis added this to the MRTK v3.0 GA milestone May 31, 2023
@AMollis AMollis self-assigned this May 31, 2023
@AMollis AMollis changed the title Investigate if Data Binding classes and if input subsystems can be removed from Core package. Investigate if input subsystems can be removed from Core package. Jun 21, 2023
@shaynie shaynie assigned shaynie and unassigned AMollis Jun 22, 2023
@shaynie shaynie closed this as completed Jun 23, 2023
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

3 participants