@joeloc: with KML import it is not an issue. In your file is on line 2492 Placemark where is a line! (somewhere in the middle of the ocean). If Locus import any file and there is just 1 track and X points, then all points are attached to this track and whole file is then imported as a single track - for me it works in same way also over "data > items".
Hmm... I see. Is there any reason why you do this? The line/track doesn't have to do anything with the points/placemarks according to the kml, they are completely separate. Why would I want them "mangled together" when importing in Locus? I'd rather have them in a separate waypoint table so I can search for names etcpp.
But maybe there are too many files out there that use one track and separate points as if they should all belong to the track? But shouldnt they be inside the track specification then in the source file?
On a related note: It would be useful if I could enable/disable rendering of named waypoints that belong to a track in the tracks rendering options. Sometimes they just get in the way of everything.
editHas the pressure sensor code been looked at recently? If I enable "automatic" calibration of the pressure sensor, I get horribly wrong altitudes at first. When GPS is enabled, first I see the correct altitude (eg 500m). Then after a second, it jumps up to 680m and then very slowly (like 1 m per second) decreases down to the correct value (500m) again.
I found out that the slowly decreasing thing is due to the altitude filter. If I disable the altitude filter, it jumps back down the correct value immediately.
That doesnt change the fact that this bogus 200m up and down jump at startup destroys the first few points of a recorded track and pretty much makes all future climbing/sinking data wrong.