Get fillGradient props

[Mike Bonner]

Ah, it was u not c thats right.  Thanks richard, that and "extending the
message path" stuff helped me get my grok on.  I think I saw c being used
for custom properties somewhere else and it stuck for some reason.

On Thu, Jul 7, 2016 at 7:51 PM, stephen barncard <
stephenREVOLUTION2 at barncard.com> wrote:

> RG:
>
> "You can quickly identify whether a variable is local or global, or whether
> it was passed in as an argument, if you preceed the descriptive name with a
> lower-case letter to determine its type."
> Char Meaning Example
>
> g
> Global variable gMyGlobal
>
> t
> Local ("temporary") variable tMyVar
>
> s
> Script-local var* (sometimes called "static") sMyVar
>
> p
> Parameter (also called an argument) pMyParam
>
> k
> Constant* kMyNumber
>
> u
> User-defined (or custom) properties uMyProp
>
>
>
>
> Stephen Barncard - Sebastopol Ca. USA -
> mixstream.org
>
> On Thu, Jul 7, 2016 at 6:50 PM, stephen barncard <
> stephenREVOLUTION2 at barncard.com> wrote:
>
> > from Richard Gaskin:
> >
> > http://www.fourthworld.com/embassy/articles/scriptstyle.html
> >
> > Stephen Barncard - Sebastopol Ca. USA -
> > mixstream.org
> >
> > On Thu, Jul 7, 2016 at 6:41 PM, Mike Bonner <bonnmike at gmail.com> wrote:
> >
> >> Somewhere I once ran across a list of suggested lc naming conventions,
> it
> >> helped me greatly. If I recall it was s for script locals, t for handler
> >> locals (t for temporary) g for globals, k for constants, c for custom
> >> properties. and I don't know if it was in the same list, but I add a
> >> trailing A for arrays.  Sure makes it easy to keep track of whats what,
> so
> >> to whoever wrote that list.. Thank you!
> >>
> >> On Thu, Jul 7, 2016 at 6:00 PM, Alex Tweedly <alex at tweedly.net> wrote:
> >>
> >> > What do you use for handler-local variables ?
> >> >
> >> > Thanks
> >> >
> >> > Alex
> >> >
> >> >
> >> > On 07/07/2016 23:16, Monte Goulding wrote:
> >> >
> >> >> On 8 Jul 2016, at 7:52 AM, Scott Rossi <scott at tactilemedia.com>
> wrote:
> >> >>>
> >> >>> I've always thought lowercase "L" is a poor choice to prefix a
> >> variable
> >> >>> name.  Is it an L? It is a capital i? Is it a pipe?
> >> >>>
> >> >> For what it’s worth we use `s` in the team for script locals. There
> are
> >> >> some older scripts like libURL that use some other prefixing
> >> conventions.
> >> >>
> >> >> Cheers
> >> >>
> >> >> Monte
> >> >> _______________________________________________
> >> >> 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
> >> >>
> >> >
> >> >
> >> > _______________________________________________
> >> > 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
> >> >
> >> _______________________________________________
> >> 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
> >>
> >
> >
> _______________________________________________
> 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
>