bluerobotics / bluerobotics/ping-viewer
ping360: don't erase old data when adjusting settings
Open
good-to-have
- Dominant language
- C++
- Stars
- 64
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
We should improve our logic so that we retain our old data by re-plotting it when the range is adjusted.
Contributor guide
Research direction
Start by locating the Ping360 range-setting entry point and the code that stores and plots scan data. Trace what happens to existing data when the range changes, then verify that the old data remains visible and is re-plotted at the adjusted range.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- data-visualization, desktop
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100