On Fri, Jun 27, 2014 at 7:08 PM, Mark Wieder wrote:
> If you at some time in the past turned on variable preservation and
> had a script variable of the same name you are now using for a handler
> variable, then that variable scope is still stored with the stack.
> Until you can compile the scrip
On Fri, Jun 27, 2014 at 7:08 PM, Mark Wieder wrote:
> So... ensure that variable preservation is unchecked, change the name
> of the variable to something without a conflict, compile the script,
> and save the stack. I think that should clear up the problem for this
> stack. Since I never use var
On Jun 27, 2014, at 7:08 PM, Mark Wieder wrote:
> Pete-
>
> Friday, June 27, 2014, 9:31:20 AM, you wrote:
>
>> A full description is in my QCC report number 10511
>
> Having now read the bug report (*very* interesting reading) my
> thinking is that this may well be connected to variable preser
Pete-
Friday, June 27, 2014, 9:31:20 AM, you wrote:
> A full description is in my QCC report number 10511
Having now read the bug report (*very* interesting reading) my
thinking is that this may well be connected to variable preservation
rather than explicitVars, even if you don't currently have
Hi Craig,
The error message "name shadows another variable" is shown as when strict
compile mode is on. It's supposed to indicate that the name of a declared
variable has already been declared somewhere else in the script, perhaps
with another local statement in the same script/handler or in a gl
On 27/06/2014 06:43, Peter Haworth wrote:
Bottom line is, this shouldn't happen, there should be no need for any
workaround.
A recent thread talked about "paper cuts". For me this is an open,
festering wound!
I absolutely agree. And it's been festering for a long time.
One annoying thing ab
Hi Mike,
My workaround is to turn off strict compilation mode, compile and turn it
back on again but that's fraught with dangerous consequences if I forget to
switch it on again.
Bottom line is, this shouldn't happen, there should be no need for any
workaround.
A recent thread talked about "paper
Not sure i'd know WHERE to do it, guess it depends on the script, but..
could you use "delete variable..." to fix the problem without having to
restart lc? Of course this would probably require you to understand the
source of the problem. Another thing I wonder about is the variable
preservation
Peter,
Can you tell me more about what this error is and does?
Craig
-Original Message-
From: Peter Haworth
To: How to use LiveCode
Sent: Thu, Jun 26, 2014 5:12 pm
Subject: Name shadows another variable
The above error has been flagged intermittently and incorrectly when
compilin
