ASCOM-Talk at Yahoo! Groups

Re: Absolute focuser move parameter

Bec Ã Fuel — Tue, 10 Nov 2009 07:27:16 GMT

... assumed to have a range of movement that begins at zero. We had to pick *some* value and zero was it. Remember, you're specifying an absolute position, not

Re: Absolute focuser move parameter

Tim Long — Mon, 09 Nov 2009 22:27:34 GMT

It is just the convention that has been adopted. Absolute focusers are assumed to have a range of movement that begins at zero. We had to pick *some* value and

Absolute focuser move parameter

Bec Ã Fuel — Mon, 09 Nov 2009 22:18:36 GMT

Hello, I was wondering why absolute moves were limited to 0:MaxStep and not to -MaxStep:+MaxStep ? _______ Christophe

Re: VB6 datatypes and specs

Chris Peterson — Mon, 09 Nov 2009 20:42:32 GMT

I didn't say that typing wasn't important, I said that using typing to enforce your input range is bad design. The ASCOM specs are as general as possible; if

Re: VB6 datatypes and specs

Bec Ã Fuel — Mon, 09 Nov 2009 18:32:50 GMT

... Are you serious ?! I totally disagree with you on this point :-( Typing is _very_ _very_ important ! If I take the MaxStep property as an example, the

Re: Can not install driver with RC7

Chuck Faranda — Mon, 09 Nov 2009 18:11:29 GMT

My previous email got posted to the group hours after it was sent, sorry it's after the fact....... Regards, Chuck Faranda http://ccdastro.com ... From: "Chuck

Re: Can not install driver with RC7

Chuck Faranda — Mon, 09 Nov 2009 17:59:48 GMT

Peter, Could this be an Inno installer issue related to comma separators? Chuck ... From: "Peter" ...

Re: Can not install driver with RC7

Peter — Mon, 09 Nov 2009 17:55:15 GMT

Tim, ... provide a method that performs this check and abstracts away all the formatting, conversion and localization issues. The client would supply their

Re: VB6 datatypes and specs

Chris Peterson — Mon, 09 Nov 2009 17:05:51 GMT

Yes, specifying the allowed range for any value is a good idea when defining specs. There's no need for unsigned integers, since signed integers will always

Re: Can not install driver with RC7

Tim Long — Mon, 09 Nov 2009 17:03:11 GMT

What would be a better (long term) solution is for the platform to provide a method that performs this check and abstracts away all the formatting, conversion

Re: VB6 datatypes and specs

Bec Ã Fuel — Mon, 09 Nov 2009 16:49:27 GMT

Peter, I've understood this issue (about long/int usage). Btw, the assembly are using Int32 integers. What I was noticing is that the missing "unsigned" type

Re: Can not install driver with RC7

Bec Ã Fuel — Mon, 09 Nov 2009 16:41:20 GMT

Oops !!! You caught me :-) Please replace the "if" line with the following : if (CheckVersion.CompareTo(new Version("5.7")) >= 0) The "5.7" string is the

Re: Can not install driver with RC7

Peter — Mon, 09 Nov 2009 16:27:27 GMT

Christophe, Would your algorithm give the correct behaviour if the platform version was 6.3 for example? Regards, Peter ... no huge work to do...

Re: VB6 datatypes and specs

Peter — Mon, 09 Nov 2009 16:23:35 GMT

Hi Christophe, ... instead of UInt64. (We could discuss the choice of Int64 instead of Int32, but it's not my purpose, here). Hopefully I can clarify the issue

Re: Can not install driver with RC7

Bec Ã Fuel — Mon, 09 Nov 2009 16:21:28 GMT

Peter, I think the warning would be welcome ;-) Btw, in C#, it's not that hard to check for versions : ================== ASCOM.Utilities.Util UtilObject = new