-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use most specific matching prefix #91
Comments
Without having had a look at the code, what you describe is what is supposed to happen. Thanks for the report, I'm going to have to have a look at this. |
Please do test if this issue is fixed on 0.3.5-beta.1 and if the rest of the controller name matching is still working 🙂 |
Thanks, I'll give it a test... |
I think this is working as expected now. Yesterday I saw LON_CTR online, and this was correctly matching up to the whole EGTT. Now, LON_N_CTR is online and that's correctly matching to EGTT-N. (p.s. I like the CATprism loading screen! 😸 ) |
Currently, LON_C_CTR and LON_N_CTR are online. However, these controllers are both only showing up under the full EGTT sector, rather than the more specific EGTT_N and EGTT_C.
I think this is driven by this part of VATspy.dat:
If I edit this file to comment out the line
EGTT|London|LON|EGTT
it works as expected.I'm not sure what logic it's currently using to match the callsign to the sector, but I wonder if it could search for the longest matching string and match against LON_C and LON_N instead of the more general LON?
The text was updated successfully, but these errors were encountered: