Mixed CDM/Non-CDM airports in list

rpuig2001 / CDM

CDM

GNU General Public License v3.0

21 stars 9 forks source link

Mixed CDM/Non-CDM airports in list #10

Closed pinatacolada closed 2 years ago

pinatacolada commented 2 years ago

When you have some airports that are CDM mixed with others that are not, the non CDM airports will ask to set Master.

In the picture, LPPT is CDM and LPFR is not.

Given that TOBT will always be equal to EOBT, I think it's beneficial to have non-CDM airports show TOBT for example in white, and the other values, TSAT TTOT etc, just blank. Otherwise we need to make a separate list just for CDM airports, and that forces using the latest euroscope beta

rpuig2001 commented 2 years ago

Hey @pinatacolada, Thank you for your input!

What would you prefere ro solve that?

A file for CDM airports, so non-CDM airport will only have TOBT.
By default no CDM airports and you must select master or slave to an specific airport.

Let me know which of this opions works better for you.

kusterjs commented 2 years ago

Best would be if the master-slave principle is no longer needed. But I understand that data of this plugin is not shared via FSD server, but externally. Also creates a risk for a single point of failure.

rpuig2001 commented 2 years ago

That will obviouly be the best way to work with! But unfortunately I still don't have enough c++ knowledge to work with other services. As soon as I have it I will apply it to the CDM. Thank you @kusterjs

kusterjs commented 2 years ago

No worries, maybe ask Juha for help. He seems to master this problem with his plugins. I believe it works primarily via scratch pad messages, that are broadcasted in a specific format.

pinatacolada commented 2 years ago

The plugin already knows which airports are CDM participants or not, through the rates.txt file and entry in the config.xml file. Any airport not present in any of these could be excluded from processing and show EOBT as TOBT and the other columns blank.

kusterjs commented 2 years ago

Just make sure the REA message function can still be used for those airports. As you know EOBTs filed by pilots are often quite inaccurate. So I really appreciate the prediction improvement that this plugin brings. This advantage should also be kept when working with non-CDM airports.

rpuig2001 commented 2 years ago

The plugin already knows which airports are CDM participants or not, through the rates.txt file and entry in the config.xml file. Any airport not present in any of these could be excluded from processing and show EOBT as TOBT and the other columns blank.

Will do it like you said, thank you!

Just make sure the REA message function can still be used for those airports. As you know EOBTs filed by pilots are often quite inaccurate. So I really appreciate the prediction improvement that this plugin brings. This advantage should also be kept when working with non-CDM airports.

REA Message Function will keep as a function for all airports ;)