XCSoar / LK8000

On Monday, March 25, 2013 7:16:20 PM UTC-7, Andrzej Kobus wrote:
On Mar 25, 10:12*pm, Andrzej Kobus wrote:

On Mar 13, 8:37*pm, Max Kellermann wrote:



On Wednesday, March 13, 2013 9:51:57 PM UTC+1, Bernie wrote:

Re #1603 'sticky zoom' or 'independent map scale'; thank you! That is something that I and my friends have long waited for and I very much appreciate you adding this overnight, fantastic work. XSoar just got better, and I already loved it!



I just uploaded XCSoar 6.6_preview1 with that feature to Google Play:https://play.google.com/store/apps/d...xcsoar.testing



(Should be visible in an hour or so)



Max, if you guys could implement PowerFlarm Mod S/Mod C traffic that

would be awesome.



Please look at this page under "Non directional Warning Screen:"



http://www.gliderpilot.org/PowerFlarmDisplays



Please look into this. I saw some exchanges on XCSoar forum on this

subject but the thread died. Thank you in advance.



Andrzej



By the way I am asking for it here as there is a ticket for it already

but priority was moved to LOW. Having this feature implemented would

allow many of us to get rid of extra displays polluting our cockpits.

To me this is more important than many other features. I guess there

are many others who think this way.

Andrzej, if you looking for using XCSoar for traffic collision instead of a dedicated display such as butterfly, you will need much more than Mode C/S support. The flarm functionality in XCSoar is mostly for buddy flying and situational awarness, but it was not designed for collision alerts as it does not have such a mode, nor audio alerts. For true and reliable collision alert, you need a dedicated display IMHO.
Having said that, if you would like to see improvement in XCSoar flarm support, you may want to add your comments and feedback to the existing tickets, or create new ones, this may attract more attention from the developers.


Ramy

On Wednesday, March 27, 2013 4:02:11 AM UTC+1, Ramy wrote:
Having said that, if you would like to see improvement in XCSoar flarm support, you may want to add your comments and feedback to the existing tickets, or create new ones, this may attract more attention from the developers.

Agree. Our bug tracker is the way to express wishes: http://bugs.xcsoar.org/newticket

Posting on RAS may or may not be seen by a XCSoar developer. On the bug tracker, you get feedback by email whenever a developer updates the ticket status, and you can subscribe to existing tickets.

(Ramy: I know your FLARM tickets, but it won't fit in XCSoar 6.6. Some of it needs some more refactoring of the internal FLARM traffic storage.)

On Mar 27, 3:40*am, Max Kellermann wrote:
On Wednesday, March 27, 2013 4:02:11 AM UTC+1, Ramy wrote:
Having said that, if you would like to see improvement in XCSoar flarm support, you may want to add your comments and feedback to the existing tickets, or create new ones, this may attract more attention from the developers.

Agree. Our bug tracker is the way to express wishes:http://bugs.xcsoar.org/newticket

Posting on RAS may or may not be seen by a XCSoar developer. On the bug tracker, you get feedback by email whenever a developer updates the ticket status, and you can subscribe to existing tickets.

(Ramy: I know your FLARM tickets, but it won't fit in XCSoar 6.6. Some of it needs some more refactoring of the internal FLARM traffic storage.)

Yes, I saw the tickets. They were downgraded to low priority and that
was the reason I posted here as I saw Max reacting to over requests.
Ramy created a couple of tickets and I did not see anyone really
responding to those tickets so I gave up.

On Wednesday, March 27, 2013 3:05:17 PM UTC+1, Andrzej Kobus wrote:
Ramy created a couple of tickets and I did not see anyone really
responding to those tickets so I gave up.

Don't give up just yet. XCSoar 6.5 was a major milestone for us: after 4 years of code cleanup, the XCSoar code base is finally "ready". Now we can focus on features, we can start to process all the tickets people have submitted.

Just look at the XCSoar 6.6 changelog (work in progress), these are the features that were implemented after only 3 weeks:

http://git.xcsoar.org/cgit/master/xc.../tree/NEWS.txt