You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If user changes the callsign OR DXCC field of an existing QSO AND there is a mismatch between the prefix and the DXCC , show alert that there might be a mismatch. There should be a clear table for correlations between the two, which is also used when an initial QSO is saved and the DXCC field is populated based on the callsign.
Bonus: Really cool would be an auto-correction of the DXCC field (and CQ/ITU Zones etc.?) if callsign or its prefix is changed. Other way around is of course not possible as there are multiple prefixed for single DXCCs.
Use case behind it: During log corrections the prefix might change but currently the DXCC field then stays the same. It is clearly wrong then. Would make it easier for the user.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
If user changes the callsign OR DXCC field of an existing QSO AND there is a mismatch between the prefix and the DXCC , show alert that there might be a mismatch. There should be a clear table for correlations between the two, which is also used when an initial QSO is saved and the DXCC field is populated based on the callsign.
Bonus: Really cool would be an auto-correction of the DXCC field (and CQ/ITU Zones etc.?) if callsign or its prefix is changed. Other way around is of course not possible as there are multiple prefixed for single DXCCs.
Use case behind it: During log corrections the prefix might change but currently the DXCC field then stays the same. It is clearly wrong then. Would make it easier for the user.
Beta Was this translation helpful? Give feedback.
All reactions