Editing Flight Plans

[frankturley]

I recently faced the task of creating a flight plan for a list of airfields that I was not familiar with. I decided to use Plan-G as the tool to do this, and I started by using the Find Airport function, and using the add to plan option in that. Because I got interrupted while doing this, I managed to add one airfield twice, which removed the black route line from the plan. I missed spotting this when it happened, so when I finished adding to my list I was baffled by the absence of the usual black line. Could I request that Plan-G gives a warning about this, as I didn't realise it would do this.

Anyway, once I had my black lines back, the next task was to inspect what looked like a childish scribble, and plot a reasonable route. This was not difficult to do by inspection, and all I had to do was re-order the list of airfields in the plan. However, this took ages, because I could only move an airfield up or down one step at a time. Could I ask that Plan-G has an addition to the right click menu to allow the insertion of the selected airfield before/after another field in the list.

Thank you for listening.

[tim arnot]

There are several things that stop the plan line from drawing - that's being looked at.

I'll put drag & drop on the list, subject to the capabilities of the underlying grid control.

[frankturley]

Thanks for your quick response Tim.

Re the disappearing black lines, the thought occurred that putting the same airfield twice consecutively in the list would result in a zero distance, and thus a divide by zero error when calculating the time for the leg - just a thought.

Re the ordering of the list, it struck me that the options of "Move to Top" and "Move to Bottom" would help; for a simple example, if there seven airfields in the list, the desired third could be moved to the top, then the second, and then the first, with something similar happening with items 5-7, at least each item would only need to be moved once - just another thought.

Thank you for listening again.

[tim arnot]

Yes, the cause in general is sub-pixel distances between consecutive nodes.

Move to top/bottom would be a good fallback position if drag/drop doesn't work out. :)