TrekBuddy

[kruch]

Late and far from being perfect, as usual - simple route navigation in map screen (only; for now).
I'm still not satisfied with route visualisation, and will very likely change it (poi marks) in final version.

Changelog

- simple route navigation
- units selection config option (metric, imperial, nautic)
- some device-specific hacks
- nmea parser, gpx log, serial/bt provider improvements
- when a wpt is reached (if distance is less than value in Wpt Proximity config setting, in meters), a sound is played - you have to create sounds subfolder in the datadir and put a file in AMR form named wpt.amr there. Sample attached. If the is not found, some default beep is played instead.

EDIT: updated 2007-07-13 11:30 CET

- fixed issues reported by Ranger and krzysiekz
- serial/bt provider + nmea parsing improved
- XML parsing fixed
- backlight control on SE
- ...

EDIT: updated 2007-07-14 13:45 CET (all build variants available)

- fixed "wpt sound not played issue"
- fixed "only one wpt shown when routing back"
- very simple route line cfg
- beginning of localization (see Settings, and have a look at http://wiki.trekbuddy.net/index.php/Localization )
- IMPORTANT! fixed parsing of negative values

EDIT: updated 2007-07-29 20:00 CET

- some more fixes
- Irish Grid support
- NMEA logging for Internal provider
- backlight control on SE
- ...

Backward compatiblity change: custom courses should cover 0-90 degrees, and the filename is arrows.png. No need for arrows2.png (I'm just going to test it on old Siemens...).

0.9.57 beta download link


Simple route navigation

When you select a waypoint list (store), you can

- navigate to single wpt (Navigate To)
- navigate along the route (Navigate Along)
- navigate backwards along the route (Navigate Back)

You can start from any wpt/rtept. Also, TB now supports GPX containting route (single, for now), ie. rte/rtept construct.

I found a weird performance problem when parsing UTF-8 encoded XML files (gpx, cms profile, ...) on N6230i (everything was fine on K750i), even if the file itself is not encoded but encoding="UTF-8" is specified in xml declaration, parsing is very very very slow. Changing the attribute to encoding="ISO-8859-1" solved it. Of course, the content encoding and encoding specification should match!

[krzysiekz]

{wpt-eta} shows weird time ex.: "08:0-36:0-29", tried with navigating to wtp and along route.
When selecting 'route back' in got application error:

[Ranger]

Bug. Start route point drawn only if routing is restarted again wit the same route.
Scenario
- load route in map mode
- move crosshair near start point
- stop routing
- load again the same route, single point drawn only (seems like Navigate to started)

[UziCorp]

I just had an error and it keeps on scrolling onto the screen:

_Event Failiure_
(code 10; result "Tue jul 10 17:42:28 GMT +00:00 2007: N 52' 46' 23" W 1' 41' 17"; 1; 4' throwable null):java.lang.NullPointerException

I press Ok, and the TB continues to function as normal, GPS is behaving as normal too.

Thanks

[guest]

i can't load this route file (created with google maps and GMapToGPX).

it's quite big and fails to load.

[guest]

can anyone test, if this utility: http://www.elsewhere.org/journal/gmaptogpx
(for google maps) produces xml-errors? i can't load files created with it into trekbuddy?

any idea?

[qw12]

The program icon is good.
But with 9.0.57 beta, I get an error each time when I try to load a route from waypoints.
Everything was OK in the previous version (9.0.57) and I could also see the route with consisting of red dots.
And I just returned back to 0.9.57

[qw12]

I took this snapshot from my SXG 75 with the first version of 0.9.57. I prepared the route with map calibrator. I think for route navigation it is very nice. You can see the route when you select Route Along. If you select Navigate to, you only see the active selected waypoint. You do not see other waypoints and the waypoint connecting line between them.
Kruch and Ranger if you do not get angry with me I want to say something: I think this version is very nice. Why do you insist on putting markers instead of waypoint names? You can also define waypoints as changigng their names. It is very easy with the map calibrator. And the waypoint is exactly the beginning of the underline of the waypoint name.

[Ranger]

[Ranger]

[qw12]

[Ranger]

Post it here, I check it.

[guest]

[Ranger]

Just look into file, extended characters (means non ascii) are changed in descriptions names.

Edit:
Yea, xml header was bad, ending question mark was not present.
You edited file by hand ?

[qw12]