PathAway Support

sorry, cant mail you that stuff atm. i am on my mountainbike for 8 more weeks and only took the PRC maps with me. my png/jpg tries are at home and offline :/.

pathaway behaves nicely so far, i only get lost very rarely .

hi scott. i am on sort of an interactive extended mountainbike trip atm (1st link on http://www.alpenzorro.de but in german!). interactive means that people keep sending me coordinates, routes, waypoints,+ of nice stuff, tracks, beaches, mountains, etc and i try to go there. problem is, these postin...

i understand that you must load jpeg completely when the map is displayed (leaving aside some tricks for partial jpeg loading). what i didnt understand was why pw went into crazyness when just scanning the directory and building the dbv. all the required info is in the cal files, no need to deal wit...

well... no help from scott yet, but i still managed to feed pw with 8gb of mapdata. it´s not for the faint hearted though, and dont try this with anything but prc. else pw will simply go crazy :/

i'm sorry... pathaway is hopelessly lost when presented with a little more data. a directory with just 300 png/pwm maps (2000x2000) makes it spend 5 (five!) minutes on startup. and not just on the first startup (building the dbv?), but on *every* startup. whats going on here? help, scott! :) ...it a...

hmmm... pw gets really nasty when stretched like that. would it help if the PNGs have only 32 instead of 64 colors? does that make any difference at all?

grmbls... it seems there are more hidden limits to that kind of thing. maybe something regarding the total number of maps as well? pathaway fucks up after a few 100 it seems, i only get "Error: Cant Read Map...: 6 (x6)". how about understandable error messages at least?

i have several hundred 2000x2000 png maps (64 colors), calibrated with pwm files. pathaway loads them mostly fine, except those that are over 3MB in size. thats strikes me as a little weird, after all, they're all 2000x2000 and should consume an equal amount of memory when loaded. is this 3MB maybe ...

hi scott. since a couple of revisions, pathaway detects when it loses contact to gps and presents a requester. nice. might i suggest a little addition here: before the requester appears, pathaway should close and reopen the gps port once and see if the connection comes back. why? this will work arou...

i just handed over my pda to show off pathaway. the guy immediately tried scrolling the map with the directional keys. pushed left a couple of times and BLAM... pathaway is rendered useless. it vainly tries to zoom out a huge map and spends an eternity eating all processor power. killed by a few key...

thanks for the export features. works nicely for publishing while on tour. how about being able to optionally export more than one item into a single gpx/kml file? like for example all checkmarked tracks instead of only the highlighted one? or even a full backup of all databases? also... a really ni...

i do have a PathAwayDBV here (about 3MB) that causes PathAway to die instantly (it freezes) whenever i try to create a new track. happens with all versions from 50 to 61. can email that file if required. the only solution (while on the road) was to delete the file and start with a fresh database, lo...

just thinking... maybe only rendering single points instead of lines from point to point might also help with the performance. lines dont matter anyway when there's a thousand track points on screen. dont know if ppcs have hw support for line rendering, the suggestion might be useless then. oh... sp...

ah ok, so it's indeed the drawing that eats the cpu. well, zooming in isnt really helpful, since you lose all idea on where to go next. its also a bit dangerous to "lose" pathaway to cpu-eating nirvana when you accidently zoom out :). glad to hear you're working on it. good luck! btw... about accide...

deactivating other tracks doesnt help. pathaway dies the sluggishness death even with just one large track in the database. and we're not talking millions of points here, just a few thousand is enough to kill the most modern pocketpc. thats really a bit weird, given that we're at over 600 mhz and a ...