Hi Albrecht,
> - I created a route with an Umlaut ("Köln") in the name, which was not
> displayed properly in the Garmin. A missing or wrong conversion somewhere?
non ASCII characters are a problem in general. To do it right, I would
need to know the character set of the device. No idea how to do that.
Just assuming it's latin1 would solve the problem for you and me, but it
will fail on devices outside latin1. I usually try to avoid special
characters.
>
> - The device doesn't beep after the upload. Is that a Garmin feature?
I never found out what it takes to make it beep. Let's say it's a
feature :).
>
> - Uploading a route creates one or more waypoints in the device which
> have just numbers as names. It would be great if the name(s) could be
> changed before the upload (if the device accepts that?).
It's a bit of a problem of limited waypoint name length. Especially the
older eTrex series is very limited. If I recall right they have 6
characters only. That's why I decided to do it with numbers only.
>
> - It would be cool if I could create a route from a waypoint (i.e a
> context and/or main menu item). The same feature should be added to
> search results (similar to the "add waypoint" feature). That's the
> *really* basic way how routes are created. Of course, the waypoint
> associated with the route should have a proper name as above.
You can select waypoints from the list to form a route, already. However
the route will create a new copy of the waypoints with the known number
scheme when uploaded.
Why is that? Well, GT is not a Garmin-only software and the concept of
transferring waypoints as part of a route is more than strange. To be
generic to other manufacturer's devices there must be no link between
the different data elements like waypoints, tracks or routes. That is
why the CDeviceGarmin instance will add waypoints on-the-fly.
If you say routes are not done very nicely I agree. But from my point of
view this is due to sloppy software engineering of Garmin. To do it
nicely you need to work around the deficiencies of the single devices.
Surely a task Garmin is willing to do in MapSource. But no way to do in
GT. Thus I consider the current implementation as a good compromise.
But, well yes, it has a stall taste like every compromise.
Btw, I never use routes. I upload waypoints and apply "goto" on the
device. Much easier :)
Oliver
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
QLandkarte-users mailing list
QLandkarte-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qlandkarte-users
