I note a bug on 2.03 referring to metric issues - I am on 2.06 (it says in "about") and there are still issues. I have MacDvie 2.02, Dive log on iPhone (4) and a load of dives synced from Divelog Mac 1.3.2. What I WANT to be able to do is sync dives from iPhone to Mac and merge the data (Suunto D6) with the GPS data from Dive log. When I try DL Manager transposes the dive data to Feet, but keeps the right numbers, then MacDive records it as real feet - at some stage I will need to delete the whole lot from Macdive and start again! But the bugs will need to go first. You know diving in metric is a lot more straightforward, the sums are easy blah blah. Well I'll be happy if it all works eventually!
I have had a problem with one dive on the "release" version of DLM (1.3) it just would not put my last logged and computed dive onto the iPhone! (hence the rest of the rigmarole!
Divelog 2.06 - Metric issues
Re: Divelog 2.06 - Metric issues
Hello awswimmer,
So sorry we've taken so long to reply to this. In theory, we're set up to receive notifications when ever there is a new post on the forums. Surprise! Guess that's not working #fail
I am not aware of any metric bugs in the current 2.0.6 release of DLM. Which of course is not to say that you haven't found one. Please elaborate on how to reproduce it/them if you can. Our default units are Metric and we convert back and forth if you have set Imperial so in theory, (heavy on the theory), Metric should be easier
But really, our user interface when importing from MacDive can be a little confusing without some explanation. First, your global preference for units in DLM is the one in the bottom left of the screen. Dive Log also has a global preference in Settings. These don't have to match, but both programs will do any necessary conversions when you input data based on what you've said your units are.
One note, there is an additional button, on the MacDive panel(s) on the top that is a *second* imperial/metric selector. This is because there are some fields in the MacDive database that are "unit-less". ie: if you enter 12 for weight, we don't know whether or not this is 12lbs or 12kilos. So this second selector is to say "if it's ambiguous, I'm Metric" (or Imperial). Practically all of the fields in MacDive have units associated with them, it was just one or two key ones that didn't so we needed an extra switch. But the key point is that your main units setting is in the bottom left.
When you say DLM 2.0.6 "transposes the dive data to feet, but keeps the right numbers" - what are you doing when this happens? I'm not following what you mean when you say "then MacDive records it as real feet" as there is no practical way to import into MacDive ... ?
As for the "release" version of DLM (1.3) - all our efforts are now going into the 2.x version so we'd like to concentrate on that so if you have the same problem, please let us know. Although it's still listed as "Beta", it's pretty much "the" release and the only thing holding us up at the moment are icon issues
Cheers,
Janice
So sorry we've taken so long to reply to this. In theory, we're set up to receive notifications when ever there is a new post on the forums. Surprise! Guess that's not working #fail
I am not aware of any metric bugs in the current 2.0.6 release of DLM. Which of course is not to say that you haven't found one. Please elaborate on how to reproduce it/them if you can. Our default units are Metric and we convert back and forth if you have set Imperial so in theory, (heavy on the theory), Metric should be easier
But really, our user interface when importing from MacDive can be a little confusing without some explanation. First, your global preference for units in DLM is the one in the bottom left of the screen. Dive Log also has a global preference in Settings. These don't have to match, but both programs will do any necessary conversions when you input data based on what you've said your units are.
One note, there is an additional button, on the MacDive panel(s) on the top that is a *second* imperial/metric selector. This is because there are some fields in the MacDive database that are "unit-less". ie: if you enter 12 for weight, we don't know whether or not this is 12lbs or 12kilos. So this second selector is to say "if it's ambiguous, I'm Metric" (or Imperial). Practically all of the fields in MacDive have units associated with them, it was just one or two key ones that didn't so we needed an extra switch. But the key point is that your main units setting is in the bottom left.
When you say DLM 2.0.6 "transposes the dive data to feet, but keeps the right numbers" - what are you doing when this happens? I'm not following what you mean when you say "then MacDive records it as real feet" as there is no practical way to import into MacDive ... ?
As for the "release" version of DLM (1.3) - all our efforts are now going into the 2.x version so we'd like to concentrate on that so if you have the same problem, please let us know. Although it's still listed as "Beta", it's pretty much "the" release and the only thing holding us up at the moment are icon issues
Cheers,
Janice
Re: Divelog 2.06 - Metric issues
OK Everything now matches and I am relatively happy with the metric/imperial stuff! 