ArduPilot / ArduPilot/MissionPlanner
optimize GUI for parameter changes (in Config Tuning > Full parameter list)
- Dominant language
- C#
- Stars
- 2.4k
- Forks
- 2.9k
- Avg merge
- 19h 16m
- Merged PRs (30d)
- 4
Description
#### Issue details
A couple suggestions for improvements for working with parameter changes in Mission Planner:
1) When making changes on parameters, the lists get's really long and difficult to handle. Please consider adding either
- a checkbox to show (filter) only those items that have been changed, but are not written to the FC yet (the green ones)
- or a "sort by" column
This would greatly help in getting a quick overview on only the changed items and thereby reduce potential errors.
2) When importing parameters from a file, a warning prompt will come for some items: "... is marked as read only and should not be changed"
Please consider adding an option to select _which_ parameters not to overwrite.
Or if that is too complicated/ cumbersome, simply add a box asking:
- leave all read-only items at their current values
- overwrite all read-only items with the imported values
3) When importing a *.param file (using the full parameter list section), there is no confirmation for successful write. (The other views do show a confirmation box).
Please consider adding a confirmation in this view as well. This would avoid ambiguity.
Thanks!
#### Version
1.3.59.2
#### Platform
[ ] All
[ ] AntennaTracker
[X] Copter
[ ] Plane
[ ] Rover
[ ] Sub
#### Airframe type
Hexacopter
#### Hardware type
Pixhawk 2.1
#### Logs
n/a
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at Mission Planner's Config Tuning > Full parameter list view and trace its parameter-change, import, and write flows. Compare its import behavior with the other views that already show a successful-write confirmation. Done means the requested changed-item filtering or sorting, read-only import choice, and successful-write confirmation are defined and implemented consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100