I have to agree though. There are other "is a <something>" statements in Rev that do not do what you would expect them to do. Because of that it is almost impossible to tell for sure, what kind of data is contained in a variable or field. For instance, 1 is a date! It's also a color!! But it's not a boolean. Hmmm... I think I would prefer a literal interpretation here. It should not be a date, color or boolean, but it if is any of those it ought to be a boolean too, at least because SQL stores boolean values this way.
Bob On Jun 27, 2010, at 1:06 PM, Malte Pfaff-Brill wrote: > Ken wrote: > >> So in my eyes, this is a bug in the "is a color" function. BTW: This is >> along with the already existing bug with the function that returns true if >> you just pass a zero to it. And similarly, you can set the backcolor (or any >> other color property) of an object to 0 and not get an error > Well, I beg to differ on describing this as a bug. Many things are colors in > rev, not only RGB values. > Any color name is, HTML Color definitions are and also revs own > representations (effective backpixel is a single number for example) are. > Is a color needs to be able to parse all of those. > > 2 cents, > Malte_______________________________________________ > use-revolution mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
