Waypoint calc - Input lost on reentering editor
See original GitHub issueDescribe your problem!
If you end the guided input, return to the waypoint edit screen and again enter the guided input its empty.
How to reproduce?
- Create a new calculated waypoint
- Tap some digits and enter valid formulas
- Click the tick mark on upper right to close the dialog
- Tap on the coordinate window again to re-enter the coordinate editor
Actual result after these steps?
- Stored equations are gone
Expected result after these steps?
Last state should be shown
Reproducible
Yes
c:geo Version
2022.01.16-NB
System information
Samsung S20, Android 12
Additional Information
No response
Issue Analytics
- State:
- Created 2 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
Map to waypoint conversion ? - DCS: F-16C Viper - ED Forums
Is there an easy way to convert a map location into a waypoint ? Hopefully Viper and Hornet.
Read more >FMS Data Input Errors | SKYbrary Aviation Safety
Time-pressure may lead to short cuts, omissions, errors and oversights in the calculation, entry and cross-checking of FMS data.
Read more >OPERATOR'S MANUAL
Manual: Entered speed is used to calculate the time-to-go. Enter speed and press . Route waypoints may be registered two ways: entering waypoint...
Read more >NSS evo3 Quick Start Guide - Tradeinn
Enter the Favorites edit mode: • Tap the Edit icon, or. • press and hold a favorite button. Edit favorite page. Delete favorite...
Read more >DCS USER MANUAL
MISSION EDITOR. The Mission Editor allows you to create missions big and small. These missions can then be used as single player missions,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ok, I understand now. This is a follow-up problem: the guide does not recognize your formula (which is a bug) and thus falls back simply showing you your current coordinate without formulas (which is a second bug -> I believe if you present it something it cannot parse it should fallback to PLAIN mode. I will also implement this).
Perfect, as its exactly how it looked when I entered it before.