Name shadows another variable error

[Peter Haworth]

Glad we're starting to home in on this longstanding issue.

Seems that Malte's recipe reproduces the problem but I see it happening in
different circumstances, not involving globals.

In my case,  a variable with the same name is defined in one or more
handlers in the scripts of several different objects,  all of which are
open in the script editor. Most of the time,  this doesn't cause a problem
but then an apply on one of the scripts suddenly throws the error.

Monte - maybe your fix handles that too?

Pete
lcSQL Software
On Nov 14, 2013 12:35 AM, "Malte Brill" <revolution at derbrill.de> wrote:

> Hi all,
>
> the easiest way for me to trigger the shadow Bug, is to change the scope
> of the variable from global to local
>
> in a card script:
>
> global tBoo
>
> on openCard
>   put "moo" into tBoo
> end openCard
>
> hit apply, change script to
>
> on openCard
>   local tBoo
>   put "moo" into tBoo
> end openCard
>
> hit apply.
>
> Cheers,
>
> Malte
>
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>