Recent content by Cobra

There is no iFly setting for turning wi-fi on or off.

Adventure Pilot doesn't usually post publicly about which features they're working on or when they'll become available in iFly, for the same reasons Garmin and FF don't: Trade secret / competitive advantage, the risk of userbase disappointment if priorities change and features are...

Maybe a bug report, and include that screenshot?

Tap the airport on the map to bring up the QuickView popup: Make sure the "APT" tab is selected (top-right corner of the QV popup). Tap "Airport Info" (lower left). You'll get a page that looks like this (note NOTAMs in the middle): Tap the [MORE] button (if present) to get a scrollable...

The engineer in me recoils at the idea of "exact" readouts, because it implies a level of precision that simply does not exist. Many ADSB-out devices are only outputting altitude to the nearest 100'. Even for those that are outputting to the nearest foot, by the time that data gets to you it...

https://adventurepilot.community.forum/threads/sticky-how-to-submit-a-bug-report-from-within-the-ifly-efb-app.26/

Yes, this is a known problem. You can read all about it here (or just go to the last post in the thread to see that it's already been reported for the version you're using): https://adventurepilot.community.forum/threads/version-13-for-windows.624/ It never hurts to submit a bug report even...

If you want a definitive answer, I'd suggest calling Adventure Pilot's Support line during normal business hours. From: https://adventurepilot.community.forum/threads/sticky-welcome-when-asking-questions-please-help-us-help-you.27/

The iFly 7xx devices use what is called a "resistive" touch screen, rather than the "capacitive" touch screen typically used on current phones and tablet devices. At the time those devices were released, resistive screens generated a much easier-to-read image in direct sunlight compared to the...

This would either: Imply that tapping somewhere on the screen changes you to "QV Mode", and that mode would persist until you clicked a "Close" button on the QV window or something. or Result in different behavior depending on which tab you select, as to close the QV window when using the...

??? No, the behavior is the same for the NAV tab. I just demonstrated it on my device.

Despite the number of words I've written on this subject now, I honestly don't feel very strongly about it one way or the other. Mostly I was just trying to share some history. Based on that history, I think the solution you propose is likely to bother some set of users. My gut feel is that...

Reasonable people can certainly disagree over which behavior will benefit the most users. I think reverting to the APT tab is the "safer" option that will serve the largest (or confuse the fewest) number of users, but unfortunately it will not be the best choice for everyone, as your post...

This does not solve the problem I described. The NAV tab is valid for every place you can tap on the map. If a user doesn't understand that QV tabs "stick", then they will become frustrated that no matter how precisely they tap on an airport, the QV pops up with a NAV result. Example:

Whether the proposed change "would be better" is a matter of personal preference. If I recall correctly, the QV tabs used to behave the way you desire. The current behavior (reverting back to the APT tab after a short time) was only implemented after one or more users complained about being...