Adding some long-lasting issues to the list of fixes required:
The value m_ShowTsVccsMiniControl in the screen setting file is always reset to 0 when ES is closed (regardless of the actual state of the mini control). ES changes this value regardless of any related user intervention.
The visibility of list items with no click function assigned & the when the tag item is the call sign cannot be set to hidden. The corresponding entry is available in the list of the “F” menu, but deselection is not possible.
Re-implement the sorting algorithm to put fields with values always on top (handle with lowest priority if the item is empty). This would help for example for the ground status list, where the sorting is already complicated because it depends on the text only and not an underlying priority number. But if you use the sequence number for sorting instead, all aircraft without a sequence number will be displayed before those with a number.
While we are at it,
Could we make the ATIS letter a data field that all controllers and plugins can see? I know this has been a request in TS and it makes sense as an ACC or APP to see ATIS letters from airports that you hadn’t connected the atis for. Also, ATIS code in PDC anyone?
Right now, the the only way the get this data is through the vatsim-data.json which is complete overkill.
Plugin interface improvements would definitely be highly appreciated as well. Here is my wish list
Set the ground state flag (currently this value can only be read)
Use case: implementation of datalink clearance where the flag is set automatically when confirmation is received
Allow to compose messages in the entry field of the command line, extending the ES default options for auto… messages
Use case: Add autotext messages for specific (plugin created) actions when the selected pilot is text only
Provide the status of a SCT file entry (active or not)
Use case: Toggle the display of specific entries (with functions, or commands) like MRVA, airspaces, terminal procedures etc. This is not possible today because the initial state of a SCT entry is not known. Therefore toggling is only possible for a specific item after a first explicit display/hide action by the plugin. And even then, the status is still not known to other plugins.
Provide all details/fields of the ESE file in existing/new functions
Use case: Customized SID/STAR lists indicating unavailable entries (due to meteo factors, airspace assignment, etc.), using the controllers radio call sign for CPDLC (composing a text message for the frequency transfer including the call sign from the ESE list)
Possibility to receive ES version information (both from the local instance and from other controllers)
Use case: plugin compatibility checks
The local instance version is required to adapt a plugin behaviour depending on the changes to the core functionalities. This would be a very handy method to ensure compatibility because you can always check the “minimum required ES version” for a plugin. Client information of other controllers can already be received via the .inf command. But it would be very helpful to access this information, too. Mainly to check what data can be exchanged/accepted by the other client.
Provide plugin list items
Use case: cooperation/interaction between plugins could be improved if data is available of the plugins loaded in the current instance. This could also allow a single plugin to make checks about the version/compatibility of all plugins.
Here’s some bigger ones that are out of reach for plugins:
Mirrored connection
Use case: Groundworks for a coordinator position whereby the connecting party sees the traffic just like the source controller. It works mostly like a non-local proxy connection (but with an extra connection/callsign to the network). Could also be handy for observing.
Tag positioning awareness
Use case: Anti-overlap logic for tags.
Native insets
Use case: Little windows of other asr files (VRC style) for better monitoring. Or even just to make it easier to have multiple ASRs on one screen without having the whole ES top and bottom bars as you would now with the current ‘‘screen position window/menu’’.
Is there any solution regarding having two different ATIS letters when running seperate DEP and ARR ATIS? Currently the METAR list can only display one.
Edit: Seemingly neither the DEP or ARR ATIS seems to be sending any ATIS letters to neighbouring possitions?
