Currently, the order of presets and contractions is defined by the order in which they were created.
This is particularly problematic with contractions as vATIS reads them from top to bottom and matches the first it finds. Sometimes, there is some overlap between the contractions (e.g. if I have a contraction for "RWY 23L" that is supposed to read "runway in use 23L" and another one for "LVP IN OPERATION, CAT III and GTO AVBL FOR RWY 23L" that is supposed to read "low visibility procedures [...] available for runway 23L") where the order matters greatly for a correct output. In the example, the "RWY 23L" contraction has to be listed after the "LVP IN OPERATION [...]" contraction, otherwise the output for the LVP statement will be "LVP in operation, cat I I I and GTO available for runway in use 23L". When updating the contractions for a given airport, I regularly have to rewrite many of the contractions in order to have them in the correct order because of this; an option to change the order of the contractions in the list would be very helpful.
For presets, it is not so much problematic as it is annoying. Due to many possible configurations and/or approach types per operating direction at most of our airports, the list of available presets can get rather long. Having the list ordered in a certain fashion (in the case of this particular profile, they are ordered by operating direction, then specific operating modes, and then approach types). When adding a new preset, I often have to do a lot of copypasting to keep the preset order from being all over the place; an option to change the order of the presets in the list would thus also be very helpful.
Currently, the order of presets and contractions is defined by the order in which they were created.
This is particularly problematic with contractions as vATIS reads them from top to bottom and matches the first it finds. Sometimes, there is some overlap between the contractions (e.g. if I have a contraction for "RWY 23L" that is supposed to read "runway in use 23L" and another one for "LVP IN OPERATION, CAT III and GTO AVBL FOR RWY 23L" that is supposed to read "low visibility procedures [...] available for runway 23L") where the order matters greatly for a correct output. In the example, the "RWY 23L" contraction has to be listed after the "LVP IN OPERATION [...]" contraction, otherwise the output for the LVP statement will be "LVP in operation, cat I I I and GTO available for runway in use 23L". When updating the contractions for a given airport, I regularly have to rewrite many of the contractions in order to have them in the correct order because of this; an option to change the order of the contractions in the list would be very helpful.
For presets, it is not so much problematic as it is annoying. Due to many possible configurations and/or approach types per operating direction at most of our airports, the list of available presets can get rather long. Having the list ordered in a certain fashion (in the case of this particular profile, they are ordered by operating direction, then specific operating modes, and then approach types). When adding a new preset, I often have to do a lot of copypasting to keep the preset order from being all over the place; an option to change the order of the presets in the list would thus also be very helpful.