The problem is, that the meaning of comment and description is not really defined. In QLGTs point of view a description is a short string, a summary. And the comment can be everything from a novel to an epic poem or a limerick.
However, other services/applications see it vice versa. A comment is a small commenting line and the description is all about the details. Imho a valid point of view. But it gets better. Some devices, services, whatever do not evaluate the one or the other. The complete <cmt> <desc> stuff in the GPX specification is defective by design. Whereas comment and description makes some kind of sense for waypoints it's of no sense for routepoints. I, personally, would call it "action" for routepoints. However the XML mafia decided to make the routepoint the same data type as a waypoint. And here we go: what tag is to be used for the action? <cmt>? <desc>? No one knows for sure. It's not defined. Thus you have to fill both fields. As the action must be something short, unless you want to read epic poems at a crossing, QLGT favours the shorter input filed, the description over the comment. But it will fill the same string to the routepoint's comment and description tag to cover all possibilities. I'll think about to add an edit dialog for routes similar to distance overlays, that lists all routpoints and gives you the opportunity to edit the action string. But that might take a while until I have a good concept for all that stuff in my mind. Oliver -------- Original-Nachricht -------- > Datum: Wed, 22 Jun 2011 08:56:40 +0100 > Von: Yannig Robert <[email protected]> > An: Oliver Eichler <[email protected]> > CC: [email protected] > Betreff: Re: [Qlandkartegt-users] Qlandkarte GT for long distance cyclists / > GPX output of routes > On 20/06/2011 22:34, Oliver Eichler wrote: > >> > >> So as you can see the comment gets overridden by the description. It > >> does not matter to me but with Murphy's law somebody will eventually > >> need the two so I thought that i would mention it. > > > > > > That is right. As I said it tests for description, comment and name. > > The first one containing text will be used. Thus the description will > > override the comment. The comment will override the name. > > > Ooooppps, I didn't read properly your first email. From my cyclist point > of view, it is fine as it is. But wouldn't it be more logical that for > the comment field QLGT tests for comment then description and finally > name but things stay as it is now for the description field. From a user > point of view it would be much more intuitive (if you fill a field it > gets carried over, if not the field gets filled with the "closest > matching" one. > > > Regards > > Yannig ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ Qlandkartegt-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
