runtime conditions for individual files

[Lorne]

Re: runtime conditions for individual files

Heh, yeah, that's a point that isn't lost on us.

Incidentally, we're planning to use a slightly different approach with the AutoPlay 4 manual...with a bit less overlap between the online help (which we'll focus more on) and the user's guide (which, time-allowing, will be more task-oriented).

At least, that's the plan...rapid application development tends to routinely shove a cattle prod into the documentation intentions around here...

[mczajka]

Re: runtime conditions for individual files

That's good to know - who reads manuals anyway - just kidding - Thanks for the help!

[Lorne]

Re: runtime conditions for individual files

The expression:

%variable% <> false

...will actually resolve to false when %variable% holds an arbitrary string.

Unless %variable% holds the string "true", the expression resolves to:

false <> false

...which is false.

Wanna know why?

From page 229 in the User's Guide:

In Setup Factory 6.0, an expression is considered true if it resolves to either the word "true" or any non-zero integer value. An expression is considered false if it resolves to the number 0 or any string other than "true".

For example, an expression that resolves to "-26" is considered true. An expression that resolves to "0" is considered false. An expression that resolves to "True" is true, and an expression that resolves to "yikes!" is false.

If you're looking to test whether the variable is empty, try using something like:

%variable% <> ""

[mczajka]

Can anyone verify that this works (runtime conditions for individual files)? I can get it to work with a variable that holds a value of TRUE, but when I evaluate an expression, that I know is TRUE, it's not working (ie: %variable% <> FALSE) the variable actually holds a directory path.