Exclude extra positions when adding a new frequency

[Adrian2k]

Did not know how to title the title 😅

Problem description:

In the AFV editor I can add multiple frequencies to show up for each position, this is a well known feature.
However recently I have gotten complains from some controllers that when they add a position, it will also add all of the other frequencies aswell, instead of just the one.

For example, for ENGM_W_APP I have the following extra stations defined:
ENGM_E_APP
ENGM_D_APP
ENGM_F_APP
ENGM_W_TWR
ENGM_E_TWR
idk maybe GND/DEL too - dont remember

When someone on ENOS_CTR needs to tempoarly take over ENGM_W_APP´s frequency, they add ENGM_W_APP as normal - however this causes the 5 other stations to appear aswell, becomming a clutter - which has to be removed one by one.

Solution wanted:

When you add a station, it will ignore the extra stations - only adding the single station you wanted.
Personally I can not think of a situation where I would want all the extra positions when adding one.

—

I hope this made sense, I couldnt remember the name AFV uses for this. VCCS maybe?

[DotWallop]

Reasonable implemention might be to add a specific indicator for when to only add the isolated frequency - for example =ENGM_W_APP. That would fall in line with other special characters that I will propose in a separate issue. :D

[pierr3]

This could be implemented and I see the use of it - will think of an UI for it

[GeorgeBarlow]

Reasonable implemention might be to add a specific indicator for when to only add the isolated frequency - for example =ENGM_W_APP. That would fall in line with other special characters that I will propose in a separate issue. :D

Could you go into a bit more detail about this, my initial thoughts to resolve this would be to include, an always checked by default, checkbox in the add station dialog titled something along the lines of Add linked radio stations, simply preventing a call to the afv-native function FetchStationVccs, rather than using indicators like =. Therefore, could you briefly expand on the benefit and extent of an indicator-like system, I understand you are planning on putting this in a separate issue, it is just my only concerns are how obvious will this system be to new users and if this is going to take some time to figure out/implement when you compare it to a simple checkbox?

Would love to hear your thoughts!