OceanLog beta version 2.1.4 Available

Please register or login

Welcome to ScubaBoard, the world's largest scuba diving community. Registration is not required to read the forums, but we encourage you to join. Joining has its benefits and enables you to participate in the discussions.

Benefits of registering include

  • Ability to post and comment on topics and discussions.
  • A Free photo gallery to share your dive photos with the world.
  • You can make this box go away

Joining is quick and easy. Log in or Register now!

rakkis:
That's over complicating the problem.

I'd be simpler to implement something like this:

A boolean called metric. Can be set by the user in preferences for a new dive's default value. Can be overridden in each dive.

The air consumption function would go:

float calculateAirConsumption (metric, tankSize, airUse() ) {
if metric { do metric calculation and return};
else {do imperial calculation and return};
}

There is no need to confuse the user with fields that they'll need to leave empty.

The issue isn't doing the proper calculations. It is when
switching back and forth between Imperial and Metric on
existing dives.
Metric and Imperial users want their tank volumes quoted
differently.... For the same tank!

The complexity in the s/w and in the GUI interface is
that when going back and forth between metric and Imperial
the users normally expect the working pressure to change
because the volumes are normally quoted with different
working pressures in metric vs Imperial.
Unfortunately, there is no way for the s/w to "guess" what an
Imperial working pressure should be if all it has is a Metric tank volume .
The s/w can easily get to "expected" metric values from an
Imperial Volume and working pressure, but it can't go the other
direction.

Depending on how its done, when a user switched from
Imperial to Metric everything would look great, but then
when they returned back to Imperial,
they would be very unhappy as all their original
working pressures and volumes would be much smaller and
not at all what they were expecting.
The numbers would not be wrong, just not at all what they were
expecting or had originally entered.

This is the dilemma.

There is no good simple answer for this.


--- bill
 
Actually there is a very simple answer for all this, have a metric & imperial version of Oceanlog - Problem solved !!
 
I am so glad I only work in metric

I still have the followig bugs
Win Vista
2.1.4 build 07.19.07

The temperature readings in the dive tab is incorrect. I get values ranging from -23 to 0 deg C. It also does not help to manually change and save the correct value. The correct value is dislayed in the table.

The SIT are incorrect. one dive shows a SIT of 00:02, Time out was 13:35 and next time in was 16:24, so it should be closer to 3 hours.


On the History page the hours for the dives in the last 6 and 12 months show 0.
The number of dives are correct.
 
Rockbrother:
The temperature readings in the dive tab is incorrect. I get values ranging from -23 to 0 deg C. It also does not help to manually change and save the correct value. The correct value is dislayed in the table.

I found this with 3 of my dives

And i have the same on the history page

Vista64 (dual processor)
 
Running Vista basic 32 bit on my laptop. Tried to do a clean install with the beta version after removing the 2.1.2 version which was at least working. This is what it told me afterward:

Run-time error '3075'

Syntax error (missing operator) in query expression 'LOCID='.

I then uninstalled the beta and re-installed the 2.1.2. It worked so I then tried to overwrite the 2.1.2 with the beta and am getting the same error. Anybody seen this error? Am I just stuck with the 2.1.2?

Thanks
 
After a little search on the web I found the following explanation for the Error 2738 msg. The web link is http://blogs.msdn.com/heaths/archiv...2738-and-2739-with-script-custom-actions.aspx


"Windows Installer Errors 2738 and 2739 with Script Custom Actions
Windows Script custom actions should be avoided. They are difficult to debug, get blocked by virus scanners, and are far more susceptible to machine state than native custom actions. That is indicated by Windows Installer error messages 2738 and 2739, which read:

2738, Could not access VBScript run time for custom action [2].
2739, Could not access JScript run time for custom action [2].
As some people have found, re-registering the runtime libraries vbscript.dll and jscript.dll will fix the errors, but that isn't always the solution."

Can anyone translate this into english for me?

I'm running XP SP2 with McAfee as my security program.

Alt is there a site link for a previous version of the software?

Regards, Keith
 
I'm trying to do an install on a Vista 32 machine. Fresh install of Vista.

OceanLog installed with no problems. However, I can't get the drivers for the USB interface to load.

Could someone provide a step-by-step of how to get the USB drivers to load under Vista32? Thanks in advance!
 
https://www.shearwater.com/products/swift/

Back
Top Bottom