Re: Changes to Msg Path from LC 7 to 8?

[hh via use-livecode]

> JLG wrote:
> ... "t" for handler-local variables, "g" for globals,
> "s" for script-locals, and "k" for constants ...
> If you adopt a system like this, you'll never have a
> naming conflict.

> Mark W. wrote:
> tExt is all I'll say ;) (thanks to Ken Ray for that one)

The LC Builder StyleGuide recommends "m" for widget static variables.
There is indeed a useful thing one can do with that, so that a lot
of things sound familiar to me(!).

private variable mE as ScriptObject
put my script object into mE

Now this is valid and unambiguous code both in LCB and LCS

send "mouseDown" to mE  ;-)


___
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

Re: Changes to Msg Path from LC 7 to 8?

[Dr. Hawkins via use-livecode]

On Thu, Jun 8, 2017 at 2:39 PM, Richard Gaskin via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Would name-spaces help?


I'm no fan of C, but I'd sure like to get its variable scoping into
livecode . . .

[*duck*]


-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
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

Re: Changes to Msg Path from LC 7 to 8?

[Tom Glod via use-livecode]

glad u worked it out Tom

On Thu, Jun 8, 2017 at 5:22 PM, J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:

> There's a spoil-sport in every crowd. :P
>
>
> On 6/8/17 4:19 PM, Mark Waddingham via use-livecode wrote:
>
>> tExt is all I'll say ;) (thanks to Ken Ray for that one)
>>
>> Warmest Regards,
>>
>> Mark.
>>
>> Sent from my iPhone
>>
>> On 8 Jun 2017, at 22:07, J. Landman Gay via use-livecode <
>>> use-livecode@lists.runrev.com> wrote:
>>>
>>> On 6/8/17 3:19 PM, tbodine via use-livecode wrote:
 Thanks for the encouragement, Richard. Looks like I'll be doing the
 "Humility
 Workout" for quite some time.
 For future list searchers who might have this same symptom, I found the
 cause: One of my stack level scripts used "theme" as a parameter name,
 but
 apparently that's a reserved term that is strictly enforced in LC 8.
 Changing that allowed all my stack scripts to run normally.

>>>
>>> That's the main reason I preface all variables with a letter, usually
>>> "t" for handler-local variables, "g" for globals, "s" for script-locals,
>>> and "k" for constants. You don't have to use the same letters but those
>>> have pretty much become the standards (some people prefer "c" for
>>> constants, but I use that for custom properties.)
>>>
>>> If you adopt a system like this, you'll never have a naming conflict.
>>>
>>> --
>>> Jacqueline Landman Gay | jac...@hyperactivesw.com
>>> HyperActive Software   | http://www.hyperactivesw.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
>>
>>
>
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software   | http://www.hyperactivesw.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

Re: Changes to Msg Path from LC 7 to 8?

[Richard Gaskin via use-livecode]

Mark Waddingham wrote:

> Jacque wrote:
>> That's the main reason I preface all variables with a letter, usually
>> "t" for handler-local variables, "g" for globals, "s" for script-
>> locals, and "k" for constants. You don't have to use the same letters
>> but those have pretty much become the standards (some people prefer
>> "c" for constants, but I use that for custom properties.)
>>
>> If you adopt a system like this, you'll never have a naming conflict.
>
> tExt is all I'll say ;) (thanks to Ken Ray for that one)

Would name-spaces help?

--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://www.FourthWorld.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

Re: Changes to Msg Path from LC 7 to 8?

[J. Landman Gay via use-livecode]

There's a spoil-sport in every crowd. :P

On 6/8/17 4:19 PM, Mark Waddingham via use-livecode wrote:

tExt is all I'll say ;) (thanks to Ken Ray for that one)

Warmest Regards,

Mark.

Sent from my iPhone


On 8 Jun 2017, at 22:07, J. Landman Gay via use-livecode 
 wrote:


On 6/8/17 3:19 PM, tbodine via use-livecode wrote:
Thanks for the encouragement, Richard. Looks like I'll be doing the "Humility
Workout" for quite some time.
For future list searchers who might have this same symptom, I found the
cause: One of my stack level scripts used "theme" as a parameter name, but
apparently that's a reserved term that is strictly enforced in LC 8.
Changing that allowed all my stack scripts to run normally.


That's the main reason I preface all variables with a letter, usually "t" for handler-local variables, "g" 
for globals, "s" for script-locals, and "k" for constants. You don't have to use the same letters but those 
have pretty much become the standards (some people prefer "c" for constants, but I use that for custom properties.)

If you adopt a system like this, you'll never have a naming conflict.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.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




--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.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

Re: Changes to Msg Path from LC 7 to 8?

[Mark Waddingham via use-livecode]

tExt is all I'll say ;) (thanks to Ken Ray for that one)

Warmest Regards,

Mark.

Sent from my iPhone

> On 8 Jun 2017, at 22:07, J. Landman Gay via use-livecode 
>  wrote:
> 
>> On 6/8/17 3:19 PM, tbodine via use-livecode wrote:
>> Thanks for the encouragement, Richard. Looks like I'll be doing the "Humility
>> Workout" for quite some time.
>> For future list searchers who might have this same symptom, I found the
>> cause: One of my stack level scripts used "theme" as a parameter name, but
>> apparently that's a reserved term that is strictly enforced in LC 8.
>> Changing that allowed all my stack scripts to run normally.
> 
> That's the main reason I preface all variables with a letter, usually "t" for 
> handler-local variables, "g" for globals, "s" for script-locals, and "k" for 
> constants. You don't have to use the same letters but those have pretty much 
> become the standards (some people prefer "c" for constants, but I use that 
> for custom properties.)
> 
> If you adopt a system like this, you'll never have a naming conflict.
> 
> -- 
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software   | http://www.hyperactivesw.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

Re: Changes to Msg Path from LC 7 to 8?

[J. Landman Gay via use-livecode]

On 6/8/17 2:35 PM, tbodine via use-livecode wrote:

Another clue... If I use the message box to call any simple stack level
handler, LC 8 changes that command to a put statement.

Example:

I type in msg box: zzShow -- a stack level handler
Msg box changes my cmd to "put zzShow" and then puts "zzShow" in the output
area.


It surprised me too the first time I saw it, but this is now the 
behavior when the message box can't find a handler.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.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

Re: Changes to Msg Path from LC 7 to 8?

[J. Landman Gay via use-livecode]

On 6/8/17 3:19 PM, tbodine via use-livecode wrote:

Thanks for the encouragement, Richard. Looks like I'll be doing the "Humility
Workout" for quite some time.

For future list searchers who might have this same symptom, I found the
cause: One of my stack level scripts used "theme" as a parameter name, but
apparently that's a reserved term that is strictly enforced in LC 8.
Changing that allowed all my stack scripts to run normally.


That's the main reason I preface all variables with a letter, usually 
"t" for handler-local variables, "g" for globals, "s" for script-locals, 
and "k" for constants. You don't have to use the same letters but those 
have pretty much become the standards (some people prefer "c" for 
constants, but I use that for custom properties.)


If you adopt a system like this, you'll never have a naming conflict.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.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

Re: Changes to Msg Path from LC 7 to 8?

[tbodine via use-livecode]

Thanks for the encouragement, Richard. Looks like I'll be doing the "Humility
Workout" for quite some time.

For future list searchers who might have this same symptom, I found the
cause: One of my stack level scripts used "theme" as a parameter name, but
apparently that's a reserved term that is strictly enforced in LC 8.
Changing that allowed all my stack scripts to run normally.

Tom B.





--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/Changes-to-Msg-Path-from-LC-7-to-8-tp4715613p4715619.html
Sent from the Revolution - User mailing list archive at Nabble.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

Re: Changes to Msg Path from LC 7 to 8?

[Tom Glod via use-livecode]

Hey Tom...I jsut yesterday switched my huge project to 8.1.4  and when
i first started migrating i had a lot of issues .

i don't have an answer to your particular problem except to say that LC 8.1
engine is much more strict and actually more trustworthy and less ambiguous.

every error i had that worked on 7.1  was my error.  be patient and i think
u will be bale to fix the issues. but trust the engine before you trust
yourself. chances are its you.

i avoided the switch because i as never sure if i was dealing with lc bug
or my own. aside from 1 ..it was all me...and a few pieces of sloppy
code.

its worth doing.


On Thu, Jun 8, 2017 at 3:35 PM, tbodine via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Another clue... If I use the message box to call any simple stack level
> handler, LC 8 changes that command to a put statement.
>
> Example:
>
> I type in msg box: zzShow -- a stack level handler
> Msg box changes my cmd to "put zzShow" and then puts "zzShow" in the output
> area.
>
> Tom
>
>
>
> --
> View this message in context: http://runtime-revolution.
> 278305.n4.nabble.com/Changes-to-Msg-Path-from-LC-7-to-8-
> tp4715613p4715614.html
> Sent from the Revolution - User mailing list archive at Nabble.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

Re: Changes to Msg Path from LC 7 to 8?

[tbodine via use-livecode]

Another clue... If I use the message box to call any simple stack level
handler, LC 8 changes that command to a put statement.

Example:

I type in msg box: zzShow -- a stack level handler
Msg box changes my cmd to "put zzShow" and then puts "zzShow" in the output
area.

Tom



--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/Changes-to-Msg-Path-from-LC-7-to-8-tp4715613p4715614.html
Sent from the Revolution - User mailing list archive at Nabble.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

Changes to Msg Path from LC 7 to 8?

[tbodine via use-livecode]

Hi all.

I am migrating a big project from LC 7.1.4 to LC 8.1.4, and hitting a wall
right away.

When my card scripts call stack level scripts directly, LC 8 throws a "can't
find handler" error. (I confirmed that the defaultStack is my main stack.)
LC 7 had no problem with this.

Example:

Card script:
on preopencard
centerThisCard
end preopencard

Stack script:
on centerThisCard
-- do stuff
end centerThisCard

Any theories or insights on why LC 8 won't do this when LC 7 will?

Thanks,
Tom B.




--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/Changes-to-Msg-Path-from-LC-7-to-8-tp4715613.html
Sent from the Revolution - User mailing list archive at Nabble.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