Difference between revisions of "Talk:Print"
imported>Heeheehee m (More info!) |
imported>StDoodle |
||
| Line 3: | Line 3: | ||
Edit: Apparently it doesn't recognize somewhat uncommon colors, like "lavender". | Edit: Apparently it doesn't recognize somewhat uncommon colors, like "lavender". | ||
--[[User:Heeheehee|Heeheehee]] 06:47, 10 March 2010 (UTC) | --[[User:Heeheehee|Heeheehee]] 06:47, 10 March 2010 (UTC) | ||
| + | |||
| + | That's true for named colors, but for numbers it appears to interpret some part of the number and chop the rest off; it was just a bit more than I wanted to look up in the moment. For instance, if you supply "#ff00000" (which is red with an extra 0), it used red; the "#" appears to make it choose the first 6 digits. However, you can leave off the "#" and it still works as expected with a 6-digit or 3-digit number; but anything else seems to be a weird substring match for which I can't find the logic.--[[User:StDoodle|StDoodle]] 13:26, 10 March 2010 (UTC) | ||
Revision as of 13:26, 10 March 2010
Re: "How does color selection work when the specified color name / entity is invalid?"
It returns with the default, black. That is, unless '> ash print("Hello world!","apple-orange");' returns a color that looks really close to black. (No, I'm not color-blind. It returns black. Even for faulty entities, like "42".)
Edit: Apparently it doesn't recognize somewhat uncommon colors, like "lavender".
--Heeheehee 06:47, 10 March 2010 (UTC)
That's true for named colors, but for numbers it appears to interpret some part of the number and chop the rest off; it was just a bit more than I wanted to look up in the moment. For instance, if you supply "#ff00000" (which is red with an extra 0), it used red; the "#" appears to make it choose the first 6 digits. However, you can leave off the "#" and it still works as expected with a 6-digit or 3-digit number; but anything else seems to be a weird substring match for which I can't find the logic.--StDoodle 13:26, 10 March 2010 (UTC)