Track export is not WYSIWYG

When exporting multiple tracks at once, the resulting gpx or kml file ignores the top-down track order as displayed in Caltopo. What it produces instead, when examining the file's code from top to bottom, is a seemingly random order of tracks. This in turn can affect how the tracks populate within other programs and apps, again with no regard for the original ordering scheme.

For example, let's say the Caltopo map contains 10 tracks, named "01_title," "02_title," "03_title" and so on. The intent is to force the sidebar list of tracks to appear in chronological order, which works as intended within Caltopo. Chances are good, however, that this ordering will be disregarded during the export process. Then, for example, when the gpx or kml is uploaded to another GPS app, that app sees only the order of tracks as coded within the file and thus creates a folder of 10 randomly ordered tracks.

Is this some sort of bug or is there a way to force the correct order of tracks during gpx / kml compile? For example, is Caltopo looking at some other filter besides alpha-numeric ordering as displayed in the GUI, such as last track edit timestamp or some such, and the user can then hack their way around the problem for now.

In geek speak, can we get a WYSIWYG track export solution in order to transfer a carefully curated dataset between platforms?