The above screen shot looks like a print screen shot ,"PrtSc" ,from a 23" large screen pc. What did you did use to run TB for this graphic??
Thanks..

lol asus transforme

Not meaning to hijack the thread but running TB on a tablet is good news..
This sounds like the ASUS TRANSFORMER, correct?
If so, have you attempted to run two applications of TB at the same time in a split screen mode? One showing CMS and the other showing your map screen
both with GPS tracking?
Thanks_________________...Blackberry Pearl 8120, OS 4.5, GPS: External Bluetooth Freedom 2000, TB ver 1.0.23
...LG Optimus 9, GPS: Internal and external, TB ver 1.2.0 Android

I still experience a tiny bug. Even though the last position is now remembered on app exit, the last zoom level (atlas) is not. So When I reopen Trekbuddy, default zoom level map is used and the last position gets twisted.
Also the bug I uploaded image for in 1.0.16 thread is still there. When I zoom too fast by + - touchscreen keys I get a Java error.

I love the new changes, Trekbuddy is much faster now and the revamped Android menu is great. Good job!

[quote="billy06"][quote]For Geocaching it would be fine to have the possibility to take a selection of waypoints (Caches) from a waypointlist and show this selection on the map.[/quote]
select show all in the waypoints menu :D[/quote]
Thank you. I now that but i dont wont select all of them only a few. Maybe 10 of 300

The Nokia N73 is very slow loading maps, but with the 1.0.17 or 1.0.18 Symbian version it´s excessively slow. It takes several minutes to load a tared map, and sometimes hang the device. TrekBuddyService 0.6.0 has been reinstalled and the external memory defragmented.

Minor case for icons bar in 2011-08-16 1.0.19 beta, on X8
Scenario
- start app with icons bar option turned on
- wait to bar is hidden
- touch left-bottom corner to display menu
- just wait a while with menu displayed (without any action), icons bar will pop-up itself for one second

on my Archos with Android 1.6 (thx again for the backport version!) there is a bug with the display resolution.
It seems like the display is larger than Trekbuddy assumes, since the map doesn't use full screen height (in both, portrait and landcape mode). After the sliding menu slides out, it partly remains visible.
Maybe this is related to the patch you added for the Archos device's display resolution detection.
The two pictures show the display content.
Maybe you can fix this in an upcoming version.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou can attach files in this forumYou can download files in this forum