TopSky plugin 2.3.1 beta 5

[Juha Holopainen 386]

Beta 5 attached.

Main changes from beta 4:

• CPDLC data file syntax updated (available data fields for datalink clearances)
  • Changes are related to providing separate frequency items for the "next frequency", one defaulting to the controller owning the sector the aircraft is in and the other to the controller issuing the clearance. The code should be compatible with the old items as well (for example if "<nfreq>" is found in a definition, it is internally changed to "NEXT FREQ <freq_next>") so a data file created for an earlier plugin version should still work without changes.
• General housekeeping in the code, possibly fixing a couple of reported issues in beta 4

TopSky231b5.zip

[Juha Holopainen 386]

For the Finnish setup, settings files attached to take advantage of new features. These will not work with earlier plugin versions.

No changes from beta 4

• TopSkySettings.txt adjusted to set maximum extended label width to 55 characters
• Tags.txt adjusted to enable extended label widths up to 60 characters
• Lists.txt adjusted (some columns widened due to code changes, new columns added)

For other setups, no changes are required to the label definitions unless an extended label width of more than 45 characters is desired. In that case, the new "part4" tag items must be added. Adjustments to the lists may be necessary for setups displaying altitude values with three digits, i.e. A030 instead of A30, as the lists will now also follow that setting (previously the altitude related list items were forced to the shorter two-digit format)

BetaSettings_Finland.zip

[Michael Eyecold 2]

Hey Juha,

when we set "Menu_MaxListItems=15", we always get CFL A40 preselected instead of 400, which it should be (XFL). When deleting this setting, it preselects 400 correctly. When changing the value to "=12", it also works fine. Thank you!!

 

Edited February 18 by Michael Eyecold

[Juha Holopainen 386]

Turns out there's a bug in the code that selects the initially visible values. With 15 items, there should be 7 values on top of the centered value. When the centered value (400 in this case) is such that there are exactly 6 values in the level list above it, the code mistakenly sets a flag that specifies the desired centered value to be below all items in the list, hence the bottom 15 items in the list will be displayed (A40 then just happens to be at the center of the visible list). The bug will also occur with any other MaxListItems value, but with some other list value depending on the max list items and the values of the items in the list. This should fortunately be an easy fix.