GlynH,
Read the 3rd to last line in my post.
I copy and pasted what AirNav Dev posted on the other topic on June 15th.
As you notice AirNav Dev had to add it to the 3.0 topic about it.
You might know it's fixed. Since you might be using a newer build of the software.
Since I haven't tested any newer software build. I can't say it's fixed or not. Since I haven't confirmed it myself. So I just say what AirNav Dev says.
Since AirNav Support hasn't said anything about it on this topic page.
I wasn't digging up a old post. Since the last post was from year 2009. Not like it was from year 2006. I sent them this topic URL in a email to them the other month. So AirNav Knew they haven't responded to this topic.
Just wanted to get this topic updated. So when users reads this topic, or do a search option on this forum. The answer can be read on the same page. Any topic should be update with the latest information. It's not digging up old posts or spouting Dis-Information like you say it is.
The topic was still 'open' without any notice of a fix.
It's all good. Any updates are good for us users. :)
Take Care,
-Brian