Overall experience with 2.2.0 had been excellent - Well done.



However there are the following points of feedback, experienced on a route between a private strip in the Manchester Low Level Corridor and Sywell, routing Ashcroft, PEDIG, potentially CT.



1) If you route via CT - partly to create a warning of crossing their centreline, as you zoom in and out, the symbol for CT NDB moves away from where the waypoint is in the planner. As you zoom out the symbol moves to East of ANSTY.



2) On the PLOG, with RNAV turned on, it gave the frequencies and Ident for HON and DTY, but not for MCT and TNT, which were the RNAV options presented for Ashcroft and PEDIG



3) On the return trip, as my destination was a Private strip, but the last waypoint before was Ashcroft, SD on an Ipaq tried to direct me off track to the East to intercept the Ashcroft centreline. Of note the wind was adverse that day for that centreline anyway. It was only about 5 degrees off track, so I was confused when following the SD, my RNAV track was diverging, until I noticed the SD was going for the centreline.



4) Partly to avoid the above point 3 ( other than routing via NANTI instead ) would it be possible to define User waypoints as Airfields - ideally including a Runway direction? If the User Interface development was too tricky / time consuming for this, could you allow additional XML in the userwaypoints.xml file - and a sample that could be edited from a template?



Thanks

Another very minor niggle with 2.2:



The print centre has buttons for 'last page' and 'next page', maybe 'previous page' would be less ambiguous than 'last page' which has caught me out a couple of times.