Skip to content

FIX: Inset the search field in the "Add supported device" popup so it no longer sits flush against the popup's left edge [UUM-150217] - #2478

Open
Pauliusd01 wants to merge 4 commits into
developfrom
fix/uum-150217-picker-search-field-inset
Open

FIX: Inset the search field in the "Add supported device" popup so it no longer sits flush against the popup's left edge [UUM-150217]#2478
Pauliusd01 wants to merge 4 commits into
developfrom
fix/uum-150217-picker-search-field-inset

Conversation

@Pauliusd01

@Pauliusd01 Pauliusd01 commented Aug 20, 2026

Copy link
Copy Markdown
Collaborator

Description

Note

This pull request was generated automatically. Please review carefully before merging.

InputControlPickerDropdown.InputControlPickerGUI.DrawSearchFieldControl(string searchString) wraps its search field in a HorizontalScope whose only leading element is the "Listen" toggle block, and that block is emitted exclusively in PickControl mode. In PickDevice mode (the "Add supported device" popup opened from Input System Package Settings > Supported Devices > "+"), there is no leading element, so the search field drew flush against the popup's left edge with no left margin while its right edge kept the base field's spacing.

The change emits a GUILayout.Space(8f) as the first element of the HorizontalScope in both modes: at the start of the PickControl branch so the "Listen" block is no longer flush against the popup's left edge, and in an else branch so the search field in PickDevice mode gets the same left inset (matching its right-side spacing). This is the same family of cosmetic-inset fix as the sibling Supported Devices list fix (UUM-150207).

Testing status & QA

  • No automated test added — the change is a cosmetic IMGUI layout inset with no observable state to assert; the nearest existing test covers dropdown tree structure, not search-field layout.
  • QA: open Project Settings > Input System Package > Supported Devices, click "+", and confirm the search field in the "Add supported device" popup is inset from the left edge and its left margin matches the right-side spacing. Repro and expected behaviour: UUM-150217.

Overall Product Risks

  • Complexity: low
  • Halo Effect: low (internal editor-only edit confined to one method, guarded so only PickDevice mode is affected)
  • Risk rating: 2/5 — Small internal editor-only cosmetic layout edit with no public API, but the ~3px inset is explicitly a to-be-tuned value whose correctness only shows visually, so the reviewer should eyeball the rendered popup margin.

Comments to reviewers

N/A

Checklist

Before review:

  • Changelog entry added.
    • Explains the change in Changed, Fixed, Added sections.
    • For API change contains an example snippet and/or migration example.
    • JIRA ticket linked, example (case %%). If it is a private issue, just add the case ID without a link.
    • Jira port for the next release set as "Resolved".
  • Tests added/changed, if applicable.
    • Functional tests Area_CanDoX, Area_CanDoX_EvenIfYIsTheCase, Area_WhenIDoX_AndYHappens_ThisIsTheResult.
    • Performance tests.
    • Integration 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.

… no longer sits flush against the popup's left edge [UUM-150217]

The search field in the "Add supported device" popup drew flush against the popup's left edge with no left margin, while its right edge kept the base field's spacing.

InputControlPickerDropdown.InputControlPickerGUI.DrawSearchFieldControl(string searchString) wraps the field in a HorizontalScope whose only leading element (the "Listen" toggle block) is emitted exclusively in PickControl mode, so in PickDevice mode nothing offset the field from the left edge. Added an else branch that emits a GUILayout.Space(3f) when the "Listen" block is absent, giving the field a left inset that matches its right-side spacing and leaving PickControl mode untouched.

Jira: https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-150217
@Pauliusd01 Pauliusd01 self-assigned this Aug 20, 2026
…50217]

Bump the PickDevice-mode search-field inset in DrawSearchFieldControl from 3px to 8px and remove the explanatory comment.

Jira: https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-150217
Add a 3px leading inset before the "Listen" toggle block in DrawSearchFieldControl so it is no longer flush against the popup's left edge in PickControl mode.

Jira: https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-150217
…217]

Bump the PickControl-mode "Listen" block inset in DrawSearchFieldControl from 3px to 8px so both modes share the same left inset.

Jira: https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-150217
@Pauliusd01
Pauliusd01 marked this pull request as ready for review August 20, 2026 05:02

@u-pr u-pr Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Harness Review

Ship it

The picker change adds a consistent left-side layout reservation before the search control in each supported picker mode, while the changelog accurately records the editor-only visual fix. I found no actionable defects in the changed behavior or release-note entry.

Reviewed commit 383dcde

🤖 Helpful? 👍/👎

@codecov-github-com

codecov-github-com Bot commented Aug 20, 2026

Copy link
Copy Markdown

Codecov Report

Attention: Patch coverage is 0% with 4 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
...Editor/ControlPicker/InputControlPickerDropdown.cs 0.00% 4 Missing ⚠️
@@            Coverage Diff            @@
##           develop    #2478    +/-   ##
=========================================
  Coverage    78.95%   78.95%            
=========================================
  Files          767      767            
  Lines       140780   140907   +127     
=========================================
+ Hits        111153   111256   +103     
- Misses       29627    29651    +24     
Flag Coverage Δ
inputsystem_MacOS_6000.0 5.30% <0.00%> (-0.01%) ⬇️
inputsystem_MacOS_6000.0_project 77.50% <0.00%> (+<0.01%) ⬆️
inputsystem_MacOS_6000.3 5.30% <0.00%> (-0.01%) ⬇️
inputsystem_MacOS_6000.3_project 77.49% <0.00%> (+<0.01%) ⬆️
inputsystem_MacOS_6000.5 5.29% <0.00%> (-0.01%) ⬇️
inputsystem_MacOS_6000.5_project 77.55% <0.00%> (+<0.01%) ⬆️
inputsystem_MacOS_6000.6 5.29% <0.00%> (-0.01%) ⬇️
inputsystem_MacOS_6000.6_project 77.55% <0.00%> (+<0.01%) ⬆️
inputsystem_MacOS_6000.7 5.29% <0.00%> (-0.01%) ⬇️
inputsystem_MacOS_6000.7_project 77.55% <0.00%> (+<0.01%) ⬆️
inputsystem_Ubuntu_6000.0 5.31% <0.00%> (-0.01%) ⬇️
inputsystem_Ubuntu_6000.0_project 77.41% <0.00%> (+<0.01%) ⬆️
inputsystem_Ubuntu_6000.3 5.31% <0.00%> (-0.01%) ⬇️
inputsystem_Ubuntu_6000.3_project 77.40% <0.00%> (+<0.01%) ⬆️
inputsystem_Ubuntu_6000.5 5.30% <0.00%> (-0.01%) ⬇️
inputsystem_Ubuntu_6000.5_project 77.46% <0.00%> (+<0.01%) ⬆️
inputsystem_Ubuntu_6000.6 5.30% <0.00%> (-0.01%) ⬇️
inputsystem_Ubuntu_6000.6_project 77.46% <0.00%> (-0.01%) ⬇️
inputsystem_Ubuntu_6000.7 5.30% <0.00%> (-0.01%) ⬇️
inputsystem_Ubuntu_6000.7_project 77.46% <0.00%> (+<0.01%) ⬆️
inputsystem_Windows_6000.0 5.30% <0.00%> (-0.01%) ⬇️
inputsystem_Windows_6000.0_project 77.62% <0.00%> (+0.06%) ⬆️
inputsystem_Windows_6000.3 5.30% <0.00%> (-0.01%) ⬇️
inputsystem_Windows_6000.3_project 77.61% <0.00%> (+0.05%) ⬆️
inputsystem_Windows_6000.5 5.29% <0.00%> (-0.01%) ⬇️
inputsystem_Windows_6000.5_project 77.68% <0.00%> (+0.05%) ⬆️
inputsystem_Windows_6000.6 5.29% <0.00%> (-0.01%) ⬇️
inputsystem_Windows_6000.6_project 77.68% <0.00%> (+0.05%) ⬆️
inputsystem_Windows_6000.7 5.29% <0.00%> (-0.01%) ⬇️
inputsystem_Windows_6000.7_project 77.68% <0.00%> (+0.05%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
...Editor/ControlPicker/InputControlPickerDropdown.cs 46.67% <0.00%> (-0.37%) ⬇️

... and 4 files with indirect coverage changes

ℹ️ Need help interpreting these results?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant