bug: Band manager damages band list when edited #838
Description
Bug Report
Platform: Windows-11-10.0.26100-SP0
CPU: Intel64 Family 6 Model 158 Stepping 10, GenuineIntel
NanoVNASaver: 0.7.3
numpy: 2.2.2
pyserial: 3.5
PySide6: 6.8.2.1
PySide6_Addons: 6.8.2.1
PySide6_Essentials: 6.8.2.1
scipy: 1.15.1
shiboken6: 6.8.2.1
importlib_metadata: 8.0.0
wheel: 0.43.0
Current behavior:
Editing or adding new rows are loosing the band name and end frequency. The new values are been stored in the wrong columns.
Expected behavior:
The new field content should be store in the same columns as it is edited.
Steps to reproduce:
Open the "Manage bands" window:
On the main window, click on "Display setup...", then, on the "Display Settings", section "Bands", click on "Manage bands".
In the "Manage bands" window we have a table with the headers "Band", "Start (Hz)" and "End (Hz)". I suppose the first column is the name of the band as strings and the other columns are the frequencies as integers.
When I click in one of the rows, or "Add row", I can edit the fields but once I finish, the new content of the first column is not used, the content of the second column goes to the first one, and the content of the third goes to the second. I imagine this is a index mismatch, a confusion about zero based indexing vs one based (just my opinion).
Related code:
N/A
Other information:
It would be nice if we could save and restore new band profiles.