Hi Bernie, I've thought about the suggestion again for a few days and I have to admit that the idea isn't all that bad. I would prefer a global "indenpendent zoom levels" option though instead of specifying it for each page. Could you do me a favor and move the ticket to the XCSoar 6.4 milestone and assign it to me? Thanks!
Turbo 2012/5/13 Bernie Baer <bb...@internode.on.net>: > Hi Turbo, > can you please elaborate on why you believe that implementing ticket #1603 > would make the user interface more complicated? > It seems that it is fairly straight forward to me: > > 1. Make the current behaviour the default, that way no-one is affected by it > unless they want to switch it on. I don't think that complicates anything? > There are already a myriad config options that are user selectable on/off, > and this would certainly be one of the less obscure ones! > 2. In Config/Look/InfoBox Modes, have a check-box in the setup for each > screen mode called " Sticky Zoom" > 3. Once selected for any one (or more) screen modes, the zoom level remains > constant on that screen (eg Cruise) unless changed, no matter how the zoom > is changed on any other screen (eg. Circling). > > How does that complicate things? I hope a developer will take an interest in > this ticket soon. > Regards, Bernie. > >> Date: Tue, 8 May 2012 23:12:51 -0700 (PDT) >> From: 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 >> Date: Wed, 9 May 2012 10:08:23 +0200 >> From: Tobias Bieniek <tobias.bien...@gmx.de> >> Subject: Re: [Xcsoar-user] Enhancement requests >> To: Ramy Yanetz <ryan...@yahoo.com> >> Cc: "xcsoar-user@lists.sourceforge.net" >> <xcsoar-user@lists.sourceforge.net> >> >> 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 >> > ------------------------------------------------------------------------------ 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
