Thread: Official Bug reports.

if one adds, or remove a destination with the right mouse button, the program DASH-PC stops. Now i can it terminate only with ctrl/alt/del over the task manager.
Without keyboard, that is rather difficult

Regards
Oliver

@zoffi as of now entering the destination from the right click is disabled due to some other problem . Once I figure that out . I will take care of this one too

While testing a route with a large detour, it keeps on re-routing constantly, with the voice guidance getting way behind. This is with 0.5 re-route distance, but after the initial 0.5 miles it keeps on doing it repeated as you move further off course.

On a large detour this resulted in a crash - this is the error message that appeared:

'The instruction at "0x525825ff" referenced memory at "0x525825ff". The memory could not by "read".'

Originally Posted by stevieg

While testing a route with a large detour, it keeps on re-routing constantly, with the voice guidance getting way behind. This is with 0.5 re-route distance, but after the initial 0.5 miles it keeps on doing it repeated as you move further off course.

On a large detour this resulted in a crash - this is the error message that appeared:

'The instruction at "0x525825ff" referenced memory at "0x525825ff". The memory could not by "read".'

Just had it again while off route, with auto re-routing off, about 5 seconds after saying 'computer zoom in' a few times.

Also still having problem with wanting to tell me to jump off the side of the motorway if I re-route while on it

I have "VOICES" tested today, so far so well - still are me no gross errors been noticeable. However remain sometimes parts of GPSWARN.JPG in the GPS.JPG-Screen (if I enter a address) visibly...

BTW: some thanks mine wishes for that realizes :-)
But I would have one still: if speed is 0, the pointer should not show a directional marker (show only "Pointer.bmp").

@steve
1) Will take a look at the crash ASAP
2) Rerouting when On a Motorway :
I have been looking at that problem for quite some time now and I don't think that it would be solved in the near future. Let me try to explain.
Assume you are traveling south on a motorway in UK so in your screen you are travelling south and you should be to your right side of the motorway on the sceen. Now you want to reroute to a place further south. Now naturally you expect the application to ask you to continue driving south but that does not seem to happen . Lets see y that happens.
You know that the GPS doesnot give you an exact location so your position on the map could be anywhere in the area covered by the circle whose radius is equal to the Max Offset Error Distance. Lets consider your position in the map could me more to the left , right , north or south from your actual position. North/south doesnot seem to be the problem but when is left or right the problem starts.
1) More towards left: Mappoint assumes you are travelling north and will ask you to take the next exit north and join the motorway in the other direction.
2) More towards right: Mappoint will ask you to take a local road and join the motorway.
Mappoint is very strict about placing the route on the motorway. We could find some workaround to snap the route to the nearest road but still this may not give you the right road. Also in case you are over a bridge and there is another road going from below you there is no way to find which road you are on as Mappoint doesnot have altitude attached to the map. One would think, why not use the direction in which you are travelling.I don't think its possible cause Mappoint does not give the user/external app the direction of the road. it has to know it for the correct route calculation but doesnot want to give it to the external app.

Hope this helps.

Satish

Problems with Mappoint 2004
One of the error you could possibly get is "The requested member of the collection does not exist. Use a valid Number or index number"
I think Mappoint made some changes in a function for parsing street address from a comma seperated string. I am currently making some changes to the UI for Address Input .

Regards
Satish

When the GPS is being initialized, I think it's still being initialised using the PC time as GMT, without applying the Timezone offset. This leads to long aquisition times.