Specifying a proximity distance for a waypoint is awkward

When I try to set a proximity distance for a waypoint, BC decides on its own if it should be meters or kilometers. Sometimes it does not accept the value at all, claiming that I have not entered a number. Also, it does not accept a European decimal sign (only a period, not a comma). Not beeing able to set the proximity distance to any value I choose makes it troublesome to use. Is there any plans for correcting this strange behaviour?

0 SUSSAMB over 11 years ago

I'm not sure how you're trying to set it but I've not getting what you are. Are you running the latest version?

Double click the waypoint then select Proximity Point, fill in the value. Is the fact it only accepts a comma a real issue? Not all EU countries use a comma :)

0 JanMart over 11 years ago

I am doing exactly that. It only Accepts a period (not a comma), but that is of minor importance. If I fill in the number 1, it decides that I try to enter 1 km. If I fill in the number 10, it insists on km too, but then I can delete the k to get meters. I find this awkward. It should simply accept my input, and not make any assumptions as to wether I want meters or kilometers. By the way: I am always using the latest Version of the SW.:)

0 BTLAAKE over 11 years ago

It should simply accept my input, and not make any assumptions as to wether I want meters or kilometers.

It makes more sense for a program to have a default unit for the case of a user not providing one. Its also faster for at least some users. If a user just entered "10" what should the program do?

You do have the option of entering ".01" or "10m". I'll grant that the autofill for the units might be a little quick.

0 JanMart over 11 years ago

That would be OK if BC ac cepted my 2 m, and did not say mkm as it does now, and then not Accept the entry.

0 Killtimer_ over 11 years ago

Does the windows version not show the default units in the dialog?

0 JanMart over 11 years ago

It does not. The screen loks quite different from Yours, like this: Is Yours from the MAC Version?

0 SUSSAMB over 11 years ago

Yes it is :)

0 JanMart over 11 years ago

Then I think Garmin has a job to do on the Windows Version!

0 SUSSAMB over 11 years ago

Not really sure it's any different really ... the Windows version just assumes you know whether you're set at kms or miles and inputs kms/metres or miles/feet as appropriate.

0 JanMart over 11 years ago

It's OK that the Windows Version knows wether I am set at metric or statute. Anything else would be strange. What I want is to know whether it takes meters or kilometers as input when BC is set up to use metric units. For some strange reasom, the m or km comes up after I have entered the number, not before.