Dominating one of all track style definition is not predictable for users

Georg D shared this problem 4 years ago
Solved

We have several places to set track styles in Locus v3.0.2. Each makes sense, each for itself is understandable, but the combination of those settings makes it quite difficult to predict the "winning" or dominating style definition - for users, but maybe also for the dev team.


Situation


Example

  • I've a GPX file containing a track with style information (green) and import it. Track styles are imported since http://www.locusmap.eu/news-in-version-2-19-0/
  • The track folder, that contains the imported track, is set to blue
  • Settings > miscellaneous> track color is set to purple

Which color will "win" or dominate?

  • I expected green as it's the most specific style definition.
  • It was blue
  • I edited the track and disabled "use style of the folder", then it was purple

So the import of track color from GPX file might still be working, but will never come into effect for the users because the imported style is dominated by other settings - I guess that was not intended by Locus dev team, thus I assume the style definitions are so complicated the devs themselfs did not understand them instantly with full consequences.


Similar questions arise in other situations

  • While recording a track, shall the color of the recording profile or of Settings > miscellaneous> track color dominate?
  • After recording and saving, shall the color of the recording profile or of Settings > miscellaneous> track color or the color of the track folder dominate?
    See also http://help.locusmap.eu/responses/recording_profiles_are_not_finished
  • maybe more, e.g. for manually created tracks, for map items containing tracks,...

Suggestion


I don't have complete design proposal, just some ideas.

  • Settings > miscellaneous> track color seems not to be required any more: During manual track creation, this style is not used. During track recording, tracks have a style because recording profiles always have a style definition. All "finished" tracks are stored in a folder and have a style, because folders always have a style definition.
    => When is this setting required?
    => Removing it will massively reduce the complexity (from 2-3 to 1-2 style definitions)
  • During import, the style from GPX file shall be set as track's own/individual style, so after deactivating "use style of the folder" for the track, the track appears in style from GPX.
  • During import from GPX, offer users the switch "use style of the folder" so they see/set the dominating style

Maybe you've further ideas :)

Best Answer
photo

Hmm nice, I thought that exists only one way to define color of track, thanks to Garmin extension <gpxx:DisplayColor>. Seems not.


So I've improved import mechanism, so your track is now yellow after import. Thanks for a help.


So in the end, color in misc settings, should be used only for a data/items files. I'll check it later more carefully and if so, it should be renamed or moved (that settings) to better place.

Comments (10)

photo
1

Hello Georg,


thanks for interesting post ...


1. green color from your GPX file is not probably correctly loaded, otherwise locus should use this color as main color for track (and also set "use folder" to false).


2. settings > misc > track color - is still needed a lot! It define color of tracks on all places, where this color is not defined. During import, over Data > items and so on.

photo
1

Thanks for your reply :)

@1: Hm, I tried again, again the track's color is not used. GPX Editor creates

<trk>

<name>2014-06-20 20:28:52 Susten</name>

<desc>0h:29m:51s | 17.1 km</desc>

<extensions>

<line xmlns="http://www.topografix.com/GPX/gpx_style/0/2">;

<color>FFFF00</color>

</line>

</extensions>

<trkseg>...


@2: When I import a track, it will be imported to a folder, and color is a required attribute of a folder, so if imported track file has no color definition, why shall it not use the folder's color definition? This one is more specific than color from settings.

If only mapItems are "left over", then the setting naming could be changed to that and become much clearer :-)

photo
1

ad 1) may you please share one track that has defined color and is not correctly imported? Becuase it should work as you mention.


ad 2) have to think about it :)

photo
1

@1: Sure :) In https://www.dropbox.com/s/qchpo0g5ktw4uro/2014-06-20_20-28-52_Susten.gpx?dl=0 the yellow style information has been defined in GPX Editor and is shown there in the preview & in the overlay on Google Maps. In Locus, it first has the style of the folder, if I edit the track to switch of folder style, purple instead of yellow is suggested as track color.

I’ve no idea how Locus expects style information to be defined in GPX files, as I can’t simply export a track with style from Locus (see http://help.locusmap.eu/responses/also-export-track-color-style-to-gpx).

photo
1

Hmm nice, I thought that exists only one way to define color of track, thanks to Garmin extension <gpxx:DisplayColor>. Seems not.


So I've improved import mechanism, so your track is now yellow after import. Thanks for a help.


So in the end, color in misc settings, should be used only for a data/items files. I'll check it later more carefully and if so, it should be renamed or moved (that settings) to better place.

photo
1

> So in the end, color in misc settings, should be used only for a

> data/items files. I'll check it later more carefully and if so, it

> should be renamed or moved (that settings) to better place.


Would be nice if you could look into this and rename the option so it's easier to understand it's purpose :) Then the original issue (better understanding which style definition dominated) would be solved.

photo
1

I'm checking places, where this parameter is used and .. well ...


I have function called "getDefaultStyleForTracks()" and this function is called 18x in whole Locus. Almost all functions that do something with tracks, use this color and width as base values if no other values are defined.


We will do during January/February check of all texts in whole app, so we will for sure, improve this one. Thanks

photo
photo
1

Thank you, I'll try it with next version :)

photo
1

fixed in v3.5.2 - after import to Locus, the track has the color defined in the PC :-)

photo
1

Perfect!

photo