-
Notifications
You must be signed in to change notification settings - Fork 330
CHANGE: Make Project-wide Actions the default for Player Input #1790
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
CHANGE: Make Project-wide Actions the default for Player Input #1790
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general looks good, and excellent you thought of Reset feature, but confused why we need to have these editor changes? Realize know that we maybe cannot do this since it would not be backwards compatible if introduced as the default value inside the component so its solved via editor?
Packages/com.unity.inputsystem/InputSystem/Plugins/PlayerInput/PlayerInput.cs
Outdated
Show resolved
Hide resolved
@ekcoh Yeah, I should have explained better the reasoning for adding the The PR fixes the above behavior. Once you press Reset, |
This event is called once the component is added for the first time https://docs.unity3d.com/2022.3/Documentation/ScriptReference/MonoBehaviour.Reset.html
Without this, changes will not be detected when a user selects "Reset" in the Component Inspector.
9540ccd to
7217ebd
Compare
|
Found this ArgumentException, steps to reproduce are niche so not sure if It's important/worth fixing if It's too hard. Steps to repro: Open the properties for the PlayerInput component -> Reset the component in the properties window (the original inspector does not need to be opened, this is not a 2 inspector bug) -> observe the error: Unity_2023-11-06_11-48-46.mp4(In the video I do the steps with your branch and then the same with Develop) |
Ahh, good catch. However, I didn't find a quick solution and, like you said, it's not critical. Seems to be very specific to that new property window and related to the "Open" button of the "project-wide actions". If I remove it the code that it's drawing the button, there's no error. Can you open a JIRA issue for it? I can investigate and fix it later. |
|
Bypassed last step of CI because I only did a changelog update. |
* Add Reset() to default values This event is called once the component is added for the first time https://docs.unity3d.com/2022.3/Documentation/ScriptReference/MonoBehaviour.Reset.html * Check for changes on "Reset" not captured by EndChangeCheck() Without this, changes will not be detected when a user selects "Reset" in the Component Inspector. * Update CHANGELOG * Add project-wide actions define * Only reference InputSystem.Editor on the Editor


Description
https://jira.unity3d.com/browse/ISX-1699
Changes made
EditorGUI.Begin/EndChangeCheckwhen users call "ResetChecklist
Before review:
Changed,Fixed,Addedsections.([case %number%](https://issuetracker.unity3d.com/issues/...)).Area_CanDoX,Area_CanDoX_EvenIfYIsTheCase,Area_WhenIDoX_AndYHappens_ThisIsTheResult.During merge:
NEW: ___.FIX: ___.DOCS: ___.CHANGE: ___.RELEASE: 1.1.0-preview.3.