-
Notifications
You must be signed in to change notification settings - Fork 362
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accuracy Enhancements #442
Comments
@gb-dursley Thanks for the feedback! Having multiple problems/enhancements bundled in one issue makes it hard to track them. Let's try to figure out which items need their own issues and then close this one out.
What device are you using? Unfortunately not all devices support vertical accuracy info, but for the ones that do you should see a "E H/V Acc" field and two values like "35.5/23.3 ft" in the Status view. I've added support for vertical accuracy to the issue for a future UI that focuses on what APIs/data a particular device supports at #313.
This is likely the above issue - if your device doesn't support vertical accuracy, you won't see this on the graph in the Accuracy pane
Not sure I understand this - could you elaborate?
Thanks for the feedback, I'll take it into account as I consider future UI changes. I have to balance ease of access too - anything you put towards the top of the screen is hard to tap when using with a single hand on most larger screen devices. |
I think "scale for grid" means a map scale bar, which has an issue open at #395, so I'm going to close this out. |
Is your feature request related to a problem? Please describe.
I'm particularly interested in Height Accuracy - but:-
Status screen only shown E H Acc - could E V Acc be added please?
Accuracy screen
scale for grid
+ or - for V error
Your...(position pane)
in EDIT mode, the SAVE button is at the edge of the pane, leading to accidental taps on the grid (changing position!) rather than the Save button. Suggest moving the button to the white space near the top right corner of the pane.
The text was updated successfully, but these errors were encountered: