Bug #2529
closedCHIRP does not allow TSQL with different Tone and ToneSQL settings
0%
Description
When I try to configure a memory entry using ToneSQL with different Rx and Tx CTCSS tones, the two settings change to the same number after committing the change, and do not stay separate. It's possible to trick the interface into allowing the multiple frequencies by clicking the dropdown for each CTCSS tone without going into properties, but the changes are not committed to memory.
Steps to reproduce:
Create a memory entry, open Properties and configure it for TSQL with two arbitrarily different tones, close the properties window, observe no change has happened.
Files
| debug.log (22.2 KB) debug.log | Edited line 5, the TSQL does not represent the separate tone values. | ||
| TSQL Bug.png (20.1 KB) TSQL Bug.png | In the first part, the current setting is shown. Secondly, I try to commit CTCSS tone changes. Third is the result. I expected the changes I committed to stick. |
Updated by Tom Hayward about 10 years ago
- Status changed from New to Rejected
You need to be in Cross tone mode to set different values for Tone and ToneSQL. Your screenshot shows you have not selected Cross for Tone Mode.
This is a lot easier to see if you turn on View > Hide Unused Fields.