What the compiler is complaining about is likely that you cannot have a
variable start with a number. This is essentially what Roger is doing with the
parameter arguement. He is putting a parameter passed by the event into a
variable called "2". I'm not sure this is a documentation issue, so much as a
fundamental understanding issue. I know a lot about those kind! :-)
Bob S
> On Sep 22, 2016, at 17:26 , Mark Wieder <ahsoftw...@sonic.net> wrote:
>
> On 09/22/2016 03:39 PM, Roger Eller wrote:
>
>> Possibly. But I learned long ago to never assume even the most basic
>> knowledge because "brain-farts" are a real problem. ;)
>
> <g> Very much agreed.
>
> But this isn't a problem with the mouseUp handler per se. When you declare a
> handler ("on xxx" or "function xxx") you can't give it explicit parameters at
> that time. And the script compiler properly complains if you do. Instead you
> give the parameter a name and can then use the name in the handler's code to
> do something, as in Mike's example. All LC handlers work exactly this way,
> and the mouseUp handler is no exception.
>
> --
> Mark Wieder
> ahsoftw...@gmail.com
>
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
