Re to Kevins request:
Hi, I agree, that the double click interval for getting into the menue
should be increased. My score in getting to the menue when I want is lower
than 50% in 6.3.3. BUT your suggestion: "Better yet, in addition remove the
"single-click gives "Map element..."
page" entirely. If I click on an airport, OK, but a single click on a
blank part of the map should not do anything" --> does not solve the
problem. (We need the map element menue.) There will always be an airspace
above us. If we tab on an empty space then this upper boundary airspace
should be shown. This is especially important in competitions where the
upper boundary of the competition boarders changes, because of crossig the
boarder to a different country.
Cheers
Chris
PS. I'm very happy that version 6.3.3 works great. Many thanks. (exept that
issue.)
Am 17.05.2012 um 23:26 schrieb "xcsoar-user-requ...@lists.sourceforge.net" <
xcsoar-user-requ...@lists.sourceforge.net>:
Send Xcsoar-user mailing list submissions to
xcsoar-user@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/xcsoar-user
or, via email, send a message with subject or body 'help' to
xcsoar-user-requ...@lists.sourceforge.net
You can reach the person managing the list at
xcsoar-user-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Xcsoar-user digest..."
Today's Topics:
1. Re: Enhancement requests (Max Kellermann)
2. Re: Ticket #1603 "Sticky zoom" (Tobias Bieniek)
3. Re: Ticket #1603 "Sticky zoom" (Bernie Baer)
4. double-click interval too short (Kevin Ford)
5. Re: Note and baro (m.underdown)
6. Re: thermal assistant and flarm radar (Pete Smith)
7. Waypointy Auto advance (STEVE WILSON)
----------------------------------------------------------------------
Message: 1
Date: Tue, 15 May 2012 18:31:42 +0200
From: Max Kellermann <m...@duempel.org>
Subject: Re: [Xcsoar-user] Enhancement requests
To: Ramy Yanetz <ryan...@yahoo.com>
Cc: "xcsoar-user@lists.sourceforge.net"
<xcsoar-user@lists.sourceforge.net>
Message-ID: <20120515163142.GA24642@Debian-60-squeeze-64-minimal>
Content-Type: text/plain; charset=us-ascii
On 2012/05/15 04:12, Ramy Yanetz <ryan...@yahoo.com> wrote:
Maybe I still need to convince, since #1974is still not assigned
although 6.4 is already in alpha test, and at least one developer
insists that it is "simply a wrong calculation and we won't have
wrong calcultions on purpose in XCSoar".
6.4 is not in alpha test. I uploaded a preview version for Android,
so people can see what we're doing, but alpha testing will begin when
it's nearly ready.
Opinions on this feature may differ, it may be a questionable feature,
but this one is trivial to implement, easy to understand, its
drawbacks should be obvious to any pilot, and it's completely
optional. Those who object don't need to use that infobox.
Max
------------------------------
Message: 2
Date: Wed, 16 May 2012 12:18:40 +0200
From: Tobias Bieniek <tobias.bien...@gmx.de>
Subject: Re: [Xcsoar-user] Ticket #1603 "Sticky zoom"
To: Bernie Baer <bb...@internode.on.net>
Cc: xcsoar-user@lists.sourceforge.net
Message-ID:
<CABEOeT=v0qpjgxrsnwh2u8x3g5gjqcdas4pcabx7oep-fqm...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
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
------------------------------
Message: 3
Date: Wed, 16 May 2012 20:52:13 +1000
From: "Bernie Baer" <bb...@internode.on.net>
Subject: Re: [Xcsoar-user] Ticket #1603 "Sticky zoom"
To: "Tobias Bieniek" <tobias.bien...@gmx.de>
Cc: xcsoar-user@lists.sourceforge.net
Message-ID: <F843A88D86FE42CDB5A5D3355586C412@bbaer>
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
reply-type=original
Hi Turbo,
I have reassigned #1603 to you, and changed the milestone to XCSoar 6.4.
A global setting sounds fine to me.
Many thanks, Bernie.
----- Original Message -----
From: "Tobias Bieniek" <tobias.bien...@gmx.de>
To: "Bernie Baer" <bb...@internode.on.net>
Cc: <xcsoar-user@lists.sourceforge.net>; <ryan...@yahoo.com>
Sent: Wednesday, May 16, 2012 8:18 PM
Subject: Re: Ticket #1603 "Sticky zoom"
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
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2171 / Virus Database: 2425/5001 - Release Date: 05/15/12
------------------------------
Message: 4
Date: Thu, 17 May 2012 08:47:44 -0500 (CDT)
From: "Kevin Ford" <f...@math.uiuc.edu>
Subject: [Xcsoar-user] double-click interval too short
To: "XCSoar Users List " <xcsoar-user@lists.sourceforge.net>
Message-ID:
<3466.98.222.48.110.1337262464.squir...@webmail.math.uiuc.edu>
Content-Type: text/plain;charset=iso-8859-1
I opened a ticket on this issue. The double-click interval is very short,
about 1/4 second in ver 6.3.1. In flight trying to double-tap with a
finger most often produces "Map element at this location" instead of
bringing up the main menu. This is incredibly annoying, as I had to hit
"Cancel" to get back to the map over and over again. Missing the
double-click interval in 6.2.6 simply did nothing and left me on the map
page, and the double-click interval was longer (at least 1/3 second on the
linux version). In flight, since "Map element..." is a single-click mode,
I thought that I wasn't tapping hard enough to register the double-tap.
Harder and harder I tapped and still the same error :-( Only
experimenting with the linux version (with a mouse) did I find the actual
problem.
Further experimenting on the ground with my PNA revealed that light taps
do not often register, and double-hard taps take longer. I suggest
increasing the double-click interval to 1/2 second or more, now that
single-clicking on blank part of the map has another function in 6.3+.
Better yet, in addition remove the "single-click gives "Map element..."
page" entirely. If I click on an airport, OK, but a single click on a
blank part of the map should not do anything (in turbulence it's easy to
accidently touch the screen if your hand is near).
Kevin Ford
------------------------------
Message: 5
Date: Thu, 17 May 2012 18:29:50 +0100
From: "m.underdown" <m.underd...@ntlworld.com>
Subject: Re: [Xcsoar-user] Note and baro
To: Tobias Bieniek <tobias.bien...@gmx.de>
Cc: xcsoar-user@lists.sourceforge.net
Message-ID: <4fb5358e.4050...@ntlworld.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
evening
Just wondering how the vario coding for xcsoar is going and when we
expecting the vario to be using the bario meter.
so i do not have to run gaggle in the back ground
thanks
martin
On 03/05/2012 16:07, Tobias Bieniek wrote:
Hi Martin
the baro sensor in these devices is used to provide the barometric
altitude and also a vario signal if nothing else is connected. The
vario signal still needs some improvements in terms of filtering, but
we are working on that.
Turbo
2012/5/3 m.underdown<m.underd...@ntlworld.com>:
Just wondering if any one has any news on getting a baro to work on the
note or the nexus
The vario with sound will also be gratefully accepted
martin
------------------------------------------------------------------------------
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
------------------------------
Message: 6
Date: Thu, 17 May 2012 21:52:55 +0100
From: Pete Smith <petejdsm...@gmail.com>
Subject: Re: [Xcsoar-user] thermal assistant and flarm radar
To: Max Kellermann <m...@duempel.org>
Cc: xcsoar-user@lists.sourceforge.net
Message-ID:
<CAG00fQS8rJN_idG_aQcNNhwyDp8XOCHsK4uLMYc=c3ghvaw...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
fyi the moving options you suggest just mean it obscures some other info
boxes, so going to put all my boxes at the top
On 4 April 2012 15:51, Max Kellermann <m...@duempel.org> wrote:
On 2012/04/04 16:49, Pete Smith <petejdsm...@gmail.com> wrote:
Is there any way of moving these up the screen so they dont obscure the
lower info boxes?
other than that i will put all my info boxes at the top.
The FLARM radar can be moved in Setup System / Look / Screen Layout.
There is no such option for the thermal assistant, other than
disabling it.
Max
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 7
Date: Thu, 17 May 2012 22:25:41 +0100 (BST)
From: STEVE WILSON <wil...@btinternet.com>
Subject: [Xcsoar-user] Waypointy Auto advance
To: "Xcsoar-user@lists.sourceforge.net"
<Xcsoar-user@lists.sourceforge.net>
Message-ID:
<1337289941.75564.yahoomail...@web87404.mail.ir2.yahoo.com>
Content-Type: text/plain; charset="iso-8859-1"
Just been trying 6.3.3 in SIM mode on my PC, prior to loading it on the
Altair this weekend, and found the following:
When I run a task using 6.2.6, the screen advances - correctly - to the
next waypoint as I enter the sector.
This does not happen with 6.3.3.? Nothing has changed - same .prf, same
task, etc, the only difference is that I'm running the 6.3.3 .exe.
?
Is this just in the PC version?? Is there a new setting I'm unaware of?
?
Thanks
Steve
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
------------------------------------------------------------------------------
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
End of Xcsoar-user Digest, Vol 71, Issue 7
******************************************
------------------------------------------------------------------------------
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
