Peter Haworth pete@... writes:
Thanks Mark. I entered a bug report on this and it is being investigated.
Meantime, I check for all the other is a possibilites first, then do my
own check for a color.
I submitted a fix for this bug today.
--
Mark Wieder
mwie...@ahsoftware.net
Great, thanks Mark.
Pete
lcSQL Software http://www.lcsql.com
On Wed, Jun 12, 2013 at 1:29 PM, Mark Wieder mwie...@ahsoftware.net wrote:
Peter Haworth pete@... writes:
Thanks Mark. I entered a bug report on this and it is being
investigated.
Meantime, I check for all the other is a
Peter Haworth pete@... writes:
As mentioned in my original post, I thought they were either three numbers
each between 0-255, a hex value, or a color name, but it sounds like it's
possible to have a 4th integer as an alpha channel? IS that correct?
I can't say whether it's right or not, but
Thanks Mark. I entered a bug report on this and it is being investigated.
Meantime, I check for all the other is a possibilites first, then do my
own check for a color.
Pete
lcSQL Software http://www.lcsql.com
On Tue, Jun 11, 2013 at 12:19 PM, Mark Wieder mwie...@ahsoftware.netwrote:
Peter
this message in context:
http://runtime-revolution.278305.n4.nabble.com/When-is-a-color-not-a-color-tp4666124p4666334.html
Sent from the Revolution - User mailing list archive at Nabble.com.
___
use-livecode mailing list
use-livecode@lists.runrev.com
On Tue, Jun 11, 2013 at 1:40 PM, BNig niggem...@uni-wh.de wrote:
on mouseUp
put 256 into tSoMany
repeat with i = 1 to tSoMany
put i tab tab Just Some Colorized Text return after tData
end repeat
delete last char of tData
lock screen
put tData into field 1
I guess the numbers 1 to 256 refer to some color look up table for 8 bit
color that is somehow in the engine?
Kind regards
Bernd
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/When-is-a-color-not-a-color-tp4666124p4666336.html
Sent from the Revolution - User
BNig niggemann@... writes:
I guess the numbers 1 to 256 refer to some color look up table for 8 bit
color that is somehow in the engine?
Exactly. There's an array of 256 RGB values in uidc.cpp.
If only one number is present, the parsecolor algorithm restricts it to a
value between 1 and 256,
byte dup
On Jun 11, 2013, at 5:27 PM, Mark Wieder wrote:
Then, for some reason I haven't wrapped my head around, it seems to multiply
those RGB values by 257 for later use.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit
Dar-
Tuesday, June 11, 2013, 4:38:14 PM, you wrote:
byte dup
Yes, I understand *what* it's doing, but I don't know why.
Seems like it's redundantly repeating itself over and over and over
again and again.
--
-Mark Wieder
mwie...@ahsoftware.net
A single integer is also true with 1 is a color also. The dictionary says
if it sees an integer it returns true to maintain compatibility with
supercard. Methinks the matching is still a bit loose. Works fine with hex
designation though.
put #ff is a color returns true as expected, and put
Thanks everyone. It seems is a color is broken. I did see the
dictionary entry about accepting a single integer as a color but this goes
beyond that.
I think I'll enter a bug report about it.
By way of context, I'm trying to identify what type of data is in custom
properties as part of a
Having an issue with using is a color
put 20,40,100,200 into tVar
put tVar is a color
...returns true. I thought that color references were either three
numbers, a hex value, or a color name.
If there is a valid color reference consisting of 4 numbers, it seems
there's a conflict between that
Subject: When is a color not a color
Having an issue with using is a color
put 20,40,100,200 into tVar
put tVar is a color
...returns true. I thought that color references were either three
numbers, a hex value, or a color name.
If there is a valid color reference consisting of 4 numbers, it seems
14 matches
Mail list logo
