lbayuk

There is a shortcut to setting the sorting order for tracks: Right-click on the Tracks sub-layer under your Track Waypoint layer name. The popup menu has the sorting options under Sort there. It works for Waypoints and Routes too.

I think this is working as designed. For tracks and routes, there are 3 choices for sort key: by name, by date, or by number. If you want complete control of the order the tracks (or routes) appear, independent of names or dates, chose to sort them by number, then you a assign a number to each track (or route) on its properties dialog. The numbers do not have to be consecutive.

Did you post the whole file you are using? When I downloaded it to inspect it, I got 81,920 bytes, but the data cuts off in the middle of a trackpoint (file line 2658). Definitely a bad GPX file.

I believe the error is in comparing to see if the new timestamp is different from the existing timestamp. In this case, the existing timestamp does not exist, which is represented by NAN. The function that compares gdoubles does not seem to work correctly when only 1 of the 2 values is NAN, and this causes viking to think that the timestamp was not changed. The following patch seems to fix it, but I did not test it nearly enough to know if it breaks 100 other things. --- src/util.c.bak 2021-11-20...

Here's a 1-line patch I tested and am now using with viking-1.8.

Waypoint Properties dialog shows wrong waypoint symbol

Using Viking-1.8 on Linux, self-compiled. Since upgrading to v1.8 I have seen an intermittent problem with waypoint symbols changing on me. I can't reproduce it on demand, so I'm not writing it as a bug, but it does happen often enough to be of concern. I have a TrackWaypoint layer with number of waypoints, some of which have a waypoint symbol assigned. What happens is I right-click on a waypoint in the sidebar, click Properties, and the dialog opens - but the waypoint has somehow acquired the symbol...

Make sure you are using a TrueType font, e.g. with SetDefaultTTFont() and/or SetUseTTF(True). The built-in (non TrueType) GD fonts do not support what you are trying to do. Test with a hard-coded string, e.g. SetXTitle("Test Omega Ω") If you did (1), (2) works, but your code still does not work, you need to see exactly what MySQL is returning for that field. It should work with either the XML decimal numeric entity, or with the UTF-8 encoding of the character.