More docs fixes #786
Merged
More docs fixes #786
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ing the action type in the Input Action editor window.
# Conflicts: # Packages/com.unity.inputsystem/Documentation~/Debugging.md # Packages/com.unity.inputsystem/Documentation~/Settings.md
Rene-Damm
reviewed
Aug 14, 2019
| NOTE: Steam controller API support is still work-in-progress. | ||
|
|
||
| For details about Steam controller API support, please consult the [Steam Support Guide](Steam.md). | ||
| The input system supports the "Standard Gamepad" mapping as specified in the [W3C Gamepad Specification](https://www.w3.org/TR/gamepad/#remapping). We also support gamepads and joysticks that are surfaced by the browser without a mapping, but that support is generally limited to detecting axes and buttons which are present, without any context as to what they mean, which means that this is generally only useful when [manually remapped by the user](HowDoI.md#-create-a-ui-to-rebind-input-in-my-game). |
Contributor
There was a problem hiding this comment.
For the latter part, might be worth clarifying how we surface them. I assume gamepads come out as Joysticks in that case? (like with HID)
Rene-Damm
reviewed
Aug 14, 2019
| |Rift| | ||
| |Daydream| | ||
| |WMR| | ||
| The input system supports any devices which implement the USB HID specification. However, for devices which don't have specific [layouts](Layouts.md) implemented in the input system, we can only surface the information available from the HID descriptor of the device, which limits how precisely we can describe a control. These devices often work best when allowing the user to manually [manually remap the controls](HowDoI.md#-create-a-ui-to-rebind-input-in-my-game). If you need to support a specific device, you can also [add your own mapping for it](HowDoI.md#-create-my-own-custom-devices). See the [manual page on HID](HID.md) for more information. |
Rene-Damm
reviewed
Aug 14, 2019
| ## Setting Up Test Assemblies | ||
|
|
||
| >NOTE: At the moment, the tests from the input system itself will be injected into user projects when following the steps here. We're working on fixing that. | ||
| Using test support requires setting up a test assembly for your tests. To do so, create a new assembly definition ("Create >> Assembly Definition") and add references to `nunit.framework.dll`, `UnityEngine.TestRunner`, and `UnityEditor.TestRunner` (as described [here](https://docs.unity3d.com/Packages/com.unity.test-framework@1.0/manual/workflow-create-test-assembly.html)) as well as `UnityEngine.Input.dll` and `UnityEngine.Input.TestFramework.dll` for the input system. |
Contributor
There was a problem hiding this comment.
Are the TestRunner references required now? Odd setup I'm thinking...
Rene-Damm
approved these changes
Aug 14, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
-Retake all screenshots with latest Input System and 19.3 UI
-New Screenshots for UI components
-Removed Future page (I don't think docs is the right place for this, also the future is too uncertain atm to commit to this in the docs)
-Feedback from last docs PR
-Fix compiling tests in 19.3
-Some 19.3 UI tweaks
-Some tweaks to existing docs pages