yep.. will be a simple click in the settings :-)
Originally Posted by Maximus
Will look into this.. thought I had solved this prob.. just testing some different code now :-)
I used 0.6 in the car today and mostly it behaved like it should.
I had a few issues though...
8 / 10 times it was impossible to route to a different address than the one you first entered.
When that happened it simply igored the new route and tried to rout you to the initial
position you had when you first launched FD.!
Yep.. sorted this one already :-)
If you loose contact with the GPS (stand-by for example) and then go into
settings >> gps >> and re-activate it again...
The speed/distance isn't updated even though things like heading, lat. / long. are.!
Will check my code again.. if It was a speed camera and it held a speed for this camera, then it does only warn once.. unless you start going over its limit then it will start bleeping at you, otherwise it will just flash.
Is the warning distance in a fixed format, miles ?
Is it working ? ;) I only got one warning per camera.!
I understand what your saying here.. say the camera is just past a long bend, then it might cause a problem as you wouldnt be heading directly for it.
Suggestion (long term project perhaps):
Take advantage of heading / direction of the speedcameras.
I know it isn't a five minute job, but you could probably keep your method
of adding cameras/parsing the database and then "just" compare the heading
before issuing the warning.!
its getting there :-)
Heck, it's useful allready !
I know its quite buggie at the mo.. but I havent come across a bug I couldnt sort out :-) its just a case of try and try again :-) I am getting better at coding now so this should help with the bugs..