Core - Use fnc_getDescriptiveName
for all ACE Action Names
#1372
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When merged this pull request will:
sys_core_fnc_getDescriptiveName
in favour offormat ["%1 Chn: %2", _radioName, api_fnc_getRadioChannel]
.I noticed yesterday that the GSA action to connect a PRC-77 displayed the radio's frequency as
[MHzKnobPos, KHzKnobPos]
, sinceapi_fnc_getRadioChannel
returns that raw data in its case.getDescriptiveName
's return is IMO better in all situations, as it will properly format channel data for all radios and also display useful info like the PTT number.Bk x Ch y
instead of the absolute (overflowing) channel number.switchChannelFast
hint) to show H and P channels as letters instead of numbers.x MHz
in HW mode andChn x NetID y
in AKW mode.30.00 MHz
for the PRC-77 and30.000 MHz
for the SEM 70 (in HW mode).