On Wed, Feb 4, 2015 at 4:17 AM, Jean-Jacques Wagner wrote:
> The "Strict Compilation Mode" option in Preferences was set (for some
> reason(
>
That's a good thing. I don't even like variable names not being
case-sensitive . . .
Also, you will find that you get good and bad days with this bug;
-- thru at that line an error
.
end Handlerx
the error says:
stack "Prozess": compilation error at line 73 (Chunk: can't create a variable
with that name (explicitVariables?)) near "ßh", char 15
2) Workaround
This was a work around, but when you have to cha
On Tue, Feb 3, 2015 at 12:35 PM, Jean-Jacques Wagner wrote:
> What to do when the compiler does not accept new variable
> (explicitvariables?, so it is well set to false). Your done, your script is
> not working anymore.
> it disappear and come again.
>
There is a very long
Jean-Jacques Wagner wrote:
> What to do when the compiler does not accept new variable
> (explicitvariables?, so it is well set to false). Your done,
> your script is not working anymore. it disappear and come again.
Short answer:
Don't use the explicitVariables global pro
Hi,
What to do when the compiler does not accept new variable (explicitvariables?,
so it is well set to false). Your done, your script is not working anymore.
it disappear and come again.
sincerely,
Jean-Jacques Wagner
___
use-livecode mailing list
use
