Skip to content

Node: add a name filter box to the configuration parameters list - #148

Open
peterbarker wants to merge 1 commit into
dronecan:masterfrom
peterbarker:pr/node-param-name-filter
Open

peterbarker wants to merge 1 commit into
dronecan:masterfrom
peterbarker:pr/node-param-name-filter

Conversation

@peterbarker

Copy link
Copy Markdown
Contributor

Node: add a name filter box to the configuration parameters list

Summary

Nodes can expose a long list of configuration parameters, which makes finding a particular one in the Node Properties window tedious. This adds a filter box above the parameter table: as you type, only parameters whose name contains the entered text are shown.

  • Matching is a case-insensitive substring match on the parameter name.
  • The box has a clear (×) button to show all parameters again.
  • Non-matching rows are hidden rather than removed, so table rows still map directly to parameter indices. Double-click / Enter to edit, and value updates after Load From File, keep working while a filter is active.
  • If a filter is entered before or during Fetch All, parameters are filtered as they arrive.

Testing

  • Offscreen Qt smoke test with a synthetic parameter list (ESC_INDEX, MOTOR_POLES, esc_rate, CAN_NODE, BEEP_VOL):
    • filter esc set before the rows arrived → ESC_INDEX, esc_rate
    • filter O → MOTOR_POLES, CAN_NODE, BEEP_VOL
    • cleared → all five shown
  • tested against an ARK x20p

🤖 Generated with Claude Code

Nodes can expose a long list of parameters, which makes finding a
particular one tedious. Add a filter box above the parameter table; only
parameters whose name contains the entered text (case-insensitive) are
shown.

Non-matching rows are hidden rather than removed, so table rows still map
directly to parameter indices and editing, Enter-to-edit and value
updates from Load From File keep working while a filter is active.
Parameters arriving during a fetch are filtered as they are added.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.

2 participants