Bug #8147
openCTRL-UP is modifying the records when selecting multiple lines
0%
Description
I have full of channel list for UV-82 (128 lines) and wanted to sort the records using CTRL-UP.
However for example when I move them to the top from the bottom application modifies the records and makes all the records same except last one. See screenshot for tas an example.
Files
Updated by Rudolph Gutzerhagen over 4 years ago
What system and version are you using?
Which version of Chirp? Attach a debug log.
Are you also able to reproduce the error on a stock configuration file (without an associated radio/driver)?
Is it possible that any other key sequence was pressed between the initial CTRL+UP, the multiple CTRL+UP, and the final CTRL+UP?
I have not been able to reproduce the problem.
Updated by Rudolph Gutzerhagen over 4 years ago
When you enter your test data in the last few rows, make sure you press ENTER to register the changes in the gtk widgets, before selecting and moving the rows. I obtained inconsistent results, but saw some evidence of overwrite of the test rows similar to what you show. It was difficult to reproduce the error; it is dependent on input. I'm not sure if this is a gtk or pygtk error. It is not a Chirp error. Hope that helps.
Updated by Rudolph Gutzerhagen over 4 years ago
Correction. I don't think it is a Chirp issue.
Updated by Erhan Aslanturk over 4 years ago
- File Baofeng_UV-82_test.img Baofeng_UV-82_test.img added
- File debug.log debug.log added
I'm running latest Chirp version on Win10. 20200718. Sorry I forgot adding log file. Now I'm attaching that.
I'm clicking on the UP key while CTRL is pressed to move rows. No other keys. I just discovered that if I move multiple rown within the visible screen it works well, but when I continue moving them out of the window (2 screens up) then this issue occurs. I'm attaching my test file and you will find the last 4 rows named TESTXXX. Select those 4 rows and try to move them at the beginning (Row 0) in one go.
Updated by Rudolph Gutzerhagen over 4 years ago
I ran the test as you suggest and got normal result.