Re: A Got-Ya

On Jan 20, 2015, at 9:14 PM, Geoff Canyon wrote: > 2. It's a feature that custom property names can be stored/referenced using > variables. For example: > > repeat for each item P in "left,top" > -- not custom properties, but the same principle applies >set the P of button "example

Re: A Got-Ya

On Thu, Jan 22, 2015 at 10:07 AM, Peter Haworth wrote: > On Wed, Jan 21, 2015 at 4:56 PM, Dr. Hawkins wrote: > > > repeat for each word theProp in "a b c" > >set the theProp of me to empty > > end repeat > > > > That's correct, but the contents of theProp variable should still be > interpret

Re: A Got-Ya

On Wed, Jan 21, 2015 at 6:00 PM, Peter Haworth wrote: > doesn't the presence of "the" and "of " indicate that > the reference is to a (custom) property not a variable > You can store the name of a custom property in a variable, even one with the same name as some other custom property. So there'

Re: A Got-Ya

On Wed, Jan 21, 2015 at 4:56 PM, Dr. Hawkins wrote: > repeat for each word theProp in "a b c" >set the theProp of me to empty > end repeat > That's correct, but the contents of theProp variable should still be interpreted as a custom property name, not a variable because of "the" and "of me"

Re: A Got-Ya

On Wed, Jan 21, 2015 at 4:00 PM, Peter Haworth wrote: > But doesn't the presence of "the" and "of " indicate that > the reference is to a (custom) property not a variable? > Not necessarily. repeat for each word theProp in "a b c" set the theProp of me to empty end repeat It's necessary to

Re: A Got-Ya

On Tue, Jan 20, 2015 at 6:14 PM, Geoff Canyon wrote: > 1. It's almost impossible to catch conflicts with custom properties. They > don't have to be mentioned by name in a script because: > But doesn't the presence of "the" and "of " indicate that the reference is to a (custom) property not a var

Re: A Got-Ya

Two things to consider: 1. It's almost impossible to catch conflicts with custom properties. They don't have to be mentioned by name in a script because: 2. It's a feature that custom property names can be stored/referenced using variables. For example: repeat for each item P in "left,top"

Re: A Got-Ya

For those who haven't read it yet I'll leave this link to Richard's excellent article here... http://www.fourthworld.com/embassy/articles/scriptstyle.html - "Some are born coders, some achieve coding, and some have coding thrust upon them." - William Shakespeare & Hugh Senior -- View this

Re: A Got-Ya

On Tue, Jan 20, 2015 at 11:44 AM, Peter Haworth wrote: > Confirmed here. Although unlikely to happen, that's a bad bug. The > presence of "the" and "of " should make it clear that a > custom property is being referenced, not a variable. > But it's nastier than that: you can't can't quote the c

Re: A Got-Ya

Confirmed here. Although unlikely to happen, that's a bad bug. The presence of "the" and "of " should make it clear that a custom property is being referenced, not a variable. Pete lcSQL Software Home of lcStackBrowser and SQLiteAd

Re: A Got-Ya

ugh. That's an ugly. I'd file a feature request to have the parser/compiler catch those for you. I am a big proponent of loose syntax, but if it's going to be loose enough that you can do THAT, then you either should get an error for misusing the token or it should be smart enough to not fail.

A Got-Ya

I just spent an 1.5 hours of "what the heck just happened". My fault but just wanted to let others know. I have a custom stack prop named "pRegion". This worked as expected except in one handler. It always returned empty. From either the handler or from the message box while the handler was being