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
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.
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
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 theCore
package, but the documentation is under theInput
package. Should the implementations be move to theInput
package.Parent Task
The text was updated successfully, but these errors were encountered: