LiveCode color map

Nonsanity form at
Mon Mar 14 11:10:54 EDT 2011

A couple of things I found odd about colornames, last time I worked with

You can't convert a colorname to it's RGB values without assigning the color
to a color property of an object, then getting the color of that object. (At
least as far as I could find.) And if you do that with a bad color name, the
RGB values you get back will be something like "Aquamarine,65,128" which is
quite odd. So it's a good idea to make sure the named color is in colornames
before applying it.

 ~ Chris Innanen
 ~ Nonsanity

On Sun, Mar 13, 2011 at 7:59 PM, J. Landman Gay <jacque at>wrote:

> On 3/13/11 6:00 PM, Bob Sneidar wrote:
>> Pretty cool. So now if I make this a library stack, could I assign
>> colors by the names in this stack? That would be cool.
> Actually the "colornames" property has been there since day one, but RR has
> always hidden it. You can set colors by name via the message box or script
> though. I haven't looked at Hugh's stack yet, but it sounds like he's making
> use of that.
> Completely aside: I often use the colornames when I want to generate random
> input for testing, or assemble a random string. "get any <char|line|word> of
> the colornames" is a quick way to do that when you just need a big list of
> text as a source. The colornames is really long, so there are lots of lines
> available.
> --
> Jacqueline Landman Gay         |     jacque at
> HyperActive Software           |
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:

More information about the Use-livecode mailing list