Dominating one of all track style definition is not predictable for users
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.
- 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,...
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 :)