Surface Interval vs. Bottom Time entry
Posted: Wed Oct 05, 2011 12:14 pm
I appreciate that a dive computer may record a dive down to the second (or less), but I'm kind of bothered by the inconsistent data format between two visibly similar controls located next to each other.
What I mean is that surface interval is entered in "hh:mm" format, where as bottom time is entered in "mm:ss" format. This is mostly a problem when I'm manually entering dives that I didn't use my computer for and forget. I'd like to think, however, that the MacDive could divine that I am not trying to log a 48 second dive to 60 feet.
If you don't like to assume that the user means 48 minutes, perhaps it could pop up a dialog asking "Did you mean 48 minutes?" with a little check box to "Don't ask again" for the users that did, in fact, intend to log a 48 second dive.
I don't think you need to necessarily even need to check for a "break" point, i.e. if they entered more than this, they meant whatever. Simply check for an integer: "1" means one minute, not one second; "10" means ten minutes, not ten seconds; "100" means 100 minutes, not 100 seconds (or 1:40, as it currently assumes). However, if they enter anything with a colon, e.g. "20:15", assume that means 20 minutes 15 seconds; "0:48" means 48 seconds, not 48 minutes.
I don't know, I guess I'm just bothered by the inconsistency. Even just a tool tip that pops up as a reminder when you hover over or select the controls would be helpful.
Thanks,
Kevin
What I mean is that surface interval is entered in "hh:mm" format, where as bottom time is entered in "mm:ss" format. This is mostly a problem when I'm manually entering dives that I didn't use my computer for and forget. I'd like to think, however, that the MacDive could divine that I am not trying to log a 48 second dive to 60 feet.
If you don't like to assume that the user means 48 minutes, perhaps it could pop up a dialog asking "Did you mean 48 minutes?" with a little check box to "Don't ask again" for the users that did, in fact, intend to log a 48 second dive.
I don't think you need to necessarily even need to check for a "break" point, i.e. if they entered more than this, they meant whatever. Simply check for an integer: "1" means one minute, not one second; "10" means ten minutes, not ten seconds; "100" means 100 minutes, not 100 seconds (or 1:40, as it currently assumes). However, if they enter anything with a colon, e.g. "20:15", assume that means 20 minutes 15 seconds; "0:48" means 48 seconds, not 48 minutes.
I don't know, I guess I'm just bothered by the inconsistency. Even just a tool tip that pops up as a reminder when you hover over or select the controls would be helpful.
Thanks,
Kevin