ReimarBauer
commented
7 years ago Original comment by Joern Ungermann (Bitbucket: joernu76, GitHub: joernu76).
The current behaviour is a probably incomplete try to have more persistent names of waypoints. Using just number, waypoint names change if the path is modified before the current waypoint. DLR-FX requires waypoint names to persist between different versions of flightplans in case that the coordinates did not change. This was realised by giving new waypoints letter as names that are associated with the coordinates and could then be selected in the drop down field for further waypoints passing through the same coordinates. Moving a waypoint obviously changes the coordinates and thus would require a new name. The current implementation is faulty in the respect that a moved waypoint is not assigned a new letter/dummy name.
So I would set the requirements to be:
- A label should be associated with fixed lon/lat coordinates
- Moving a waypoint to a different lon/lat coordinate should discard the current label
- Moving a waypoint to a labeled location should use the label
- Labels should be persistent on a per-flighttrack basis
More questionable are the following requirements as they could be solved by proper user intervention (i.e. manually labeling waypoints before communicating the flight plan):
- Waypoints should be given unique, unchanging labels (currently semi-implemented for insertiong, but not coordinate change)
- One might include some "magnetic" shift towards labeled locations when moving locations with the mouse
Original report by Jens-Uwe Grooß (Bitbucket: grooss, GitHub: grooss).
If waypoints are created by the insert button, they are labelled as letters 'A', 'B', etc. If then the location is changed (by mv button or editing the table view coordinates), the label changes to numbers (no Location label in the table view). This is somewhat confusing, and I would suggest leaving out the automatic creation of the label letters.