- Messages
- 34,981
- Country

Thanks to help from Jim Vile I have realized that ADE is passing through information from the airport record that I had not planned to pass through. This is especially true of Approach Data. Because ADE does not process this data the deleteRecord for Approaches is set to False. As a result you will get two sets of Approach data for an airport modified by ADE. The default set and the same set passed unseen by ADE. This is not what is intended and has all sorts of unwanted side effects such as seeing the approaches twice in the GPS. This just underlines my concern over how easy it is to get things screwed up.
This is just a warning of what is happening, although I would hope that no one is using ADE in a 'production mode' since it is really still in the middle of the development cycle.
Having said that the next build of ADE will remove all Approach data from any files loaded into it. It will also do the same with Terminal Waypoints.
I plan at a later stage to develop a 'safe' visual tool for Approach Design (assuming that Jim and others will save me from my own ignorance when required
) But I do not think it right to retain this in ADE.
If you feel that I am wrong then please let me know !
This is just a warning of what is happening, although I would hope that no one is using ADE in a 'production mode' since it is really still in the middle of the development cycle.
Having said that the next build of ADE will remove all Approach data from any files loaded into it. It will also do the same with Terminal Waypoints.
I plan at a later stage to develop a 'safe' visual tool for Approach Design (assuming that Jim and others will save me from my own ignorance when required
If you feel that I am wrong then please let me know !