-
Notifications
You must be signed in to change notification settings - Fork 313
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
FIX: The "Add Control Scheme..." popup now requires explicit Save/Close user action (case ISXB-1131) #2044
Conversation
…t Save/Close user action (case ISXB-1131) o Previously clicking outside the popup window (anywhere in the editor) would close the popup window. o This would leave a new blank (unnamed, orphaned) control scheme populating the UI - this was confusing. o Now this popup will persist until the user explictly chooses to Save or Cancel.
…p fix (case ISXB-1131)
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.
Testing this on Alex's machine shows the issue is resolved, whist the other related issue is not regressed. It also seems a more intuitive UX flow.
… closing parenthesis.
Adding QA |
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.
LGTM. Checked:
- trying to interact with things within the asset while the control scheme popup is open (you can't, It's fully static. Would be great if it blinked when you click outside it just like on Windows, but I don't think that's a thing we can use in UITK)
- entering play mode while it is open (it auto closes and refreshes the window, which I think is fine)
- closing the input window while the popup is still there (same as the play mode scenario)
- basic functionality of adding/removing/editing schemes
…se user action (case ISXB-1131) (#2044) * [Input System] The "Add Control Scheme..." popup now requires explicit Save/Close user action (case ISXB-1131) o Previously clicking outside the popup window (anywhere in the editor) would close the popup window. o This would leave a new blank (unnamed, orphaned) control scheme populating the UI - this was confusing. o Now this popup will persist until the user explictly chooses to Save or Cancel. * [Input System] Added CHANGELOG entry for "Add Control Scheme..." popup fix (case ISXB-1131) * [Input System] Fix typo in CHANGELOG entry - removed extraneous final closing parenthesis. * [Input System] Licensing failure - try limiting to version 2021.3.45f
Description
Previously clicking outside the popup window (anywhere in the editor) would close the popup window.
This would leave a new blank (unnamed, orphaned) control scheme populating the UI - this was confusing.
Now this popup will persist until the user explicitly chooses to Save or Cancel.
Testing status & QA
Manually testing the UI using the reproduction steps provided.
Local and automated testing.
Overall Product Risks
Comments to reviewers
This issue manifested when the Input System started using the newer UIToolkit implementation of its UI.
It was a result of fixing another issue in this PR.
Discussions with @Pauliusd01 and @lyndon-unity led to this choice of behaviour change of this popup window:
Checklist
Before review:
Changed
,Fixed
,Added
sections.Area_CanDoX
,Area_CanDoX_EvenIfYIsTheCase
,Area_WhenIDoX_AndYHappens_ThisIsTheResult
.During merge:
NEW: ___
.FIX: ___
.DOCS: ___
.CHANGE: ___
.RELEASE: 1.1.0-preview.3
.After merge: