As I already mentioned #1974 is simply a wrong calculation and we won't have wrong calcultions on purpose in XCSoar.
#1561 isn't all that trivial to implement and #1603 is making the user interface more complicated IMHO. Any developer is free to choose to implement either one of those tickets, but they are not very high on my personal todo list. Turbo 2012/5/9 Ramy Yanetz <ryan...@yahoo.com>: > XCSoar developers, > > The enhancement listed below (not all mine) are still in the wishlist > bucket. I believe they should all be easy to implement and will be very > valuable. Can I make an appeal to consider those for 6.4? > > #1561 OLC distance should be calculated from release to next waypoint > #1974 Need instantaneous HW/TW calculation using TAS-GS when available > #1603: Require zoom function independent for each map page > > Thanks, > > Ramy > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Xcsoar-user mailing list > Xcsoar-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xcsoar-user > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Xcsoar-user mailing list Xcsoar-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcsoar-user
