So, I had a chance to fly iFly in some thunderstormy weather yesterday. As I picked my way from airport to airport, I had a chance to use the Info Box more.
First, I wanted go "Direct" from from present position to the airport in the Info Box. I didn't see a "Direct" button up front, and didn't discover that it's two clicks away until on the ground later. (I thought I had clicked on "Flight Planning" in flight. If I did, it didn't do in flight what it's doing on the ground.)
Okay, now that I know where it is, I can live with 2 clicks, although I would make it so that there's a D with an Arrow thru it to the left of the Airport's name at the top of the box for going Direct. (Same with any Info Box title, be it a VOR, NDB, Int or WP.)
But for this thread, the Close X icon needs to be moved to the top right of the Info Box, just like where it is for the large VP window and just where it is in Windows, Linux, Mac OS, etc. If it can't be in the title bar, it should be where the "APT" symbol is, and drop everything down one.
It's another one of those small nits, but our eyes shouldn't have to hunt around in flight to find how we close a box. It's more difficult to use the GUI when "X marks the spot" is different from box to box.
P.S. What is the purpose of the "APT" symbol? If I click on a VOR, expecting frequency, High power, Low power, or Terminal, and perhaps useable radials (from the AFD), the APT icon is still there. It's just not highlighted. Which might not be obvious, because it's still readable.
I see that the blue outline follows the underlying "Info" hit. But I don't see what purpose that serves. Nor am I going to notice that nice embellishment in flight.
Therefore, I suggest getting rid of the APT icon symbol altogether and instead, putting "K" in front of the airport ID on the left. That would distinguish it from, say, a VOR with same 3 letter ID, as is the case at KFLG. The pretty blue outline can go around the entire box, making life easier for Brian.
(BTW, if iFly ever does implement this VOR feature, then how will you deal with airports that are co-located with VORs? Like KFLG? How will you toggle thru possible underlying "hits"?)
|