TrekBuddy

[Ranger]

Small problem with azimuth to wpt roundings.

Scenario
1. Set wpt in map mode
2. Place crosshair on the east side of wpt to have azimuth value 269, distance to wpt should be selected to have few vertical pixel positions for 269 angle
3. Move crosshair by pixel up and down, you will see roundings to 180 instead of 270

Wpt recording fix value
I found in few of many recorded wpts fix value -1 when number of visible satelites was > 5. Probably caused by provider itself.
Can we have some kind of displayed info about fix value when wpt is recorded ? Or hear a sound like "no 3D fix" in such case ?

(Important, sometimes no chance to visit wpt place once again)

[kruch]

Updated known issues in the announcement post.

@wowi: could you elaborate a bit on nautical units, please, so that I do not have to google? how would you like it? Thanks!
1 km ~ 1.852 nautical mile? abbreviations? ..

[Ranger]

@Kruch
Sample java code not only for nautical units conversion can be found in GPSAPI

http://sweb.cz/happyBOY78/GPSAPI.zip

[wowi]

Nautical units: 1 nautical mile = 1.852 km exactly. I would implement a checkbox "Nautical units" in the Settings. When it is enabled, distances should be in nautical miles instead of km, altitude still in m, velocity in knots (kn) = nautical miles per hour. In the extended OSD line then instead of the altitude the course would be more interesting on a sailing boat. I am not sure about abbreviation of nautical mile, may be M is fine according to Wikipedia.

@Ranger: thankyou, very interesting code.

wowi

[wowi]

"crosshair redraw on SXG75 when scrolling" - sorry, may be I described the bug not accurate . When scrolling, the crosshair is shown correctly, but if the crosshair position moves due to a recalculated GPS position, the bug occures.

[kruch]

thanks - now I know! ... mystery solved... ufff

[kruch]

[kruch]

b2

- fixed known issues (except for slow scrolling on S65)
- also wpt recording fix value should be fixed
- new: Options->Desktop->nautical view

I hope that hh:mm:ss format of {time} won't break your CMS...

Please let me know how it works for you, so that we can have a final 0.9.55 release, with doc update etc

[guest]

[krzysiekz]

Maps scrolling works even without pressing arrow keys. When arrow is pressed ~2sec screen is scrolled until opposite direction is selected, or '5' key is pressed.

[wowi]

Thankyou, crosshair redrawing on SXG75 is now ok and nautical view works with extended OSD line showing velocity in kn and course.

Nautical view:
- Please could you also show the distance to a destination waypoint in nautical miles with 3 digits after the decimal point instead of m?

- Is it possible to display the velocity in kn with one digit after the decimal point?

- And here is a general point that could help to use TB in practice:
My phone has some keys that immediately start unwanted actions. Could you make a key lock, for example with the number '9' key that is not yet used, as far as I know?

[kruch]

[krzysiekz]

'7' and '9' are used when atlas is loaded, '9' selects maps in current layer. Maybe '0'? It's change cross image now ( and could be done from menu).

[kruch]

[kruch]

I often change crosshair with '0', and changing it in Options would not be very comfortable.... so... '* is not used in MapView, but - then you could not lock the keyboard in HPS or CMS.... I don't know..

EDIT: Proposal - use '0' for day/night mode switching in all screens, so that '*' can be used for keylock....