In Galaxy (and I believe in Constellation) the explicit vars property
is only set during a compile, and then it is set according to the
explicit var setting that is "attached" to the object being compiled.
This is a Galaxy/Constellation convention.
SO...I don't think it's entirely accurate to say Constellation or
Galaxy has its own setting, but rather the object itself. Small
difference, but an important one.
Best,
Jerry Daniels
Tool makers for the 21st century
http://www.daniels-mara.com
On Oct 12, 2006, at 10:23 AM, Stephen Barncard wrote:
I had this problem and found out it was Constellation, it has it's
own settings for explicitvariables. But you didn't mention it, I know.
Hmmm. Recently, 2.7.2 on OS X started to behave as if
explicitvariables was set to true. Perfectly functioning scripts
opened in the editor would generate unquoted literal errors and
moaning about undeclared variables.
I today moved to 2.7.4, confident that the problem would go away,
but it hasn't - 'put the explicitvariables' in the message box
returns false. Setting it to false changes nothing.
I found nothing on this in the archives since 2003. Que pasa?
Best Wishes,
David Glasgow
Carlton Glasgow Partnership
http://www.i-psych.co.uk
--
stephen barncard
s a n f r a n c i s c o
- - - - - - - - - - - -
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
