bluerobotics / bluerobotics/ping-viewer
Ping360 persistent start; connection and settings
- Dominant language
- C++
- Stars
- 64
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
Most users from my point of view has one unit, either Ping1D or Ping360.
Each time starting Pingviewer You have to connect and then change your settings like scan angle, range etc.
Suggestion: have Pingviewer to automatic startup; connect and resume last settings.
For support of more complex systems, when needed:
Add an checkbox in settings like "manual connection and settings"
That checkbox makes everyting like it work today.
Of course the checkbox could be other way around, check box when you do not want persistent startup.
Bo
Contributor guide
Research direction
The issue does not name files, tests, or entry points. Start by locating Ping Viewer’s startup connection flow and the settings persistence or restoration code; done means a single-unit user can reconnect automatically and resume the last scan settings, while a manual option preserves the current behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100