Wrong order when connecting points with line (frontend does not respect timestamps correctly) about frontend

[brummbrum]

Wow! Thank you so much for fixing this so quickly!! Tested it immediately and it seems to work really well now even with some very messed up .rec files (I frequently run into these situations when connectivity of the clients gets lost in the backcountry). Actually I am surprised how well the manual sorting works and how elegantly you were able to fit it in. I have no clue about js and the .sort method and was a bit worried how it would treat entries without timestamps but it seems to behave gracefully. otrecorder required a little bit of code around this, https://github.com/owntracks/recorder/blob/master/listsort.c. I have not noticed a performance hit in my environment even with large data sets. It seems that in my setup (ot-recorder runs on a raspberry pi) the ot-recorder api is the bottleneck rather than the js sorting.

[linusg]

Thanks for the bug report! I've seen this happen before, but I never investigated and just assumed that the entries were in chronological order but accuracy was low - which might not have been the case! The bug is fixed and I'll make a new release shortly. My only concern is how well the manual sorting performs on large datasets, but we'll see.

[linusg]

Released in 2.10.0, Docker image should be built shortly.