Guys and gals...
let's start making a habit of checking the isxvg version in the scripts we write and post. heck, if you want, you can also load the extension (if not already loaded) from the script itself.
Example:
Obviously, if your script requires things in a newer build of ISXVG (version DATEc instead of DATEb, for example) you'd have to change that in your code. You could also make that string a variable.
Doing these two things in your scripts will filter out ALOT of "issues" people will have with your scripts.
let's start making a habit of checking the isxvg version in the scripts we write and post. heck, if you want, you can also load the extension (if not already loaded) from the script itself.
Example:
Code:
function Main()
{
; Force the loading of ISXVG if not already loaded:
ext -require isxvg
; Check the version of ISXVG and if less than the version between the []'s, error out and end the script
; This calculation in this example should allow ISXVG 20070215a and above. Anything older will fail.
if ${ISXVG.Version.Compare[20070215a]}<0
{
echo Go away until you update to ISXVG version 20070215a or later!
return
}
...
rest of your script goes here.... blah blah
...
}Doing these two things in your scripts will filter out ALOT of "issues" people will have with your scripts.