InputSystem
InputSystem copied to clipboard
NEW: Input System Profiler Module
Description
Made a draft implementation of a Profiler Module for the Input System based on lack of observability to work as an aid in understanding system mechanics. Hopefully could work as an embryo of something more refined if considered a good idea.
Testing status & QA
Just a prototype at this point. Try it out and suggest or contribute to this PR to make it more useful.
Overall Product Risks
Some more work likely need to be done to InputManager.OnUpdate to make that method cleaner and this work more reliably.
Might not be possible to merge unless minimum Unity version requirement is changed to 2020.1. (Profiler package dependency)
- Complexity: Small
- Halo Effect: Medium
Comments to reviewers
At this point mainly looking for feedback and suggestions since this was unplanned work.
Checklist
Before review:
- [ ] Changelog entry added.
- Explains the change in
Changed,Fixed,Addedsections. - For API change contains an example snippet and/or migration example.
- JIRA ticket linked, example (case %<ID>%). If it is a private issue, just add the case ID without a link.
- Jira port for the next release set as "Resolved".
- Explains the change in
- [ ] Tests added/changed, if applicable.
- Functional tests
Area_CanDoX,Area_CanDoX_EvenIfYIsTheCase,Area_WhenIDoX_AndYHappens_ThisIsTheResult. - Performance tests.
- Integration tests.
- Functional tests
- [ ] Docs for new/changed API's.
- Xmldoc cross references are set correctly.
- Added explanation how the API works.
- Usage code examples added.
- The manual is updated, if needed.
During merge:
- [ ] Commit message for squash-merge is prefixed with one of the list:
NEW: ___.FIX: ___.DOCS: ___.CHANGE: ___.RELEASE: 1.1.0-preview.3.
After merge:
- [ ] Create forward/backward port if needed. If you are blocked from creating a forward port now please add a task to ISX-1444.