Keith G Posted May 10, 2016 Report Share Posted May 10, 2016 Problem seems to be with caches having longitude W 000o ... e.g. GC5N20E The displayed coords say E 000o, but should be W 000o. However, 'Navigate to Cache' displays cache in the correct location on the map. If you then create a user waypoint with appropriate longitude, e.g. W 000o, it is immediately displayed as E, though again it shows correctly on the map. Next, if you edit the waypoint, and save without actually making any changes, then again display this waypoint, it now has moved many miles to the east (i.e. E000). There is no issue with W 001o Quote Link to comment Share on other sites More sharing options...
Nic Hubbard Posted May 11, 2016 Report Share Posted May 11, 2016 Thanks Keith for reporting this, and thanks for the GC code. I will look into getting this fixed. Quote Link to comment Share on other sites More sharing options...
Keith G Posted May 12, 2016 Author Report Share Posted May 12, 2016 Wow - that was a rapid response. Thank you. It has certainly fixed the problem for the GC code I mentioned. However, I played a bit more and believe that the problem still exists, but in reverse. So if I create and save a user waypoint E 000 xx.xxx, it now changes it to W 000 xx.xxx, but displays in the correct position on the map (E 000). Similarly, if I edit and save without making changes, then the waypoint appears to move to W 000 on the map. I believe I have also found another bug with waypoints, but I'll check some more and e-mail support. Hope you get some sleep! Quote Link to comment Share on other sites More sharing options...
Nic Hubbard Posted May 13, 2016 Report Share Posted May 13, 2016 Thanks. I will reopen that issue and do some more digging. Quote Link to comment Share on other sites More sharing options...
Keith G Posted June 15, 2016 Author Report Share Posted June 15, 2016 Nic, I can confirm that this is now fixed. Thanks again. Quote Link to comment Share on other sites More sharing options...
Nic Hubbard Posted June 15, 2016 Report Share Posted June 15, 2016 Nic, I can confirm that this is now fixed. Thanks again. Glad to hear it. Fixed in the beta version, correct? Quote Link to comment Share on other sites More sharing options...
Keith G Posted June 15, 2016 Author Report Share Posted June 15, 2016 Yes, current beta - 1.1.4 (6) Nic Hubbard 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.