 |
Author |
Topic: why does fill() tint bitmap images? (Read 564 times) |
|
trip
 
 
|
why does fill() tint bitmap images?
« on: Sep 12th, 2003, 6:58am » |
|
i don't know if this is a bug or a "feature", but when I use a fill() command, if a bitmap has been moved using translate() (and the whole push pop thing), the bitmap gets tinted with the fill color.
take a look at: http://www.negativespace.org/cmendoza/bugs_me/
one bitmap (the yellowish one) is imaged just fine. The other (which is actually the same image) is imaged when you press the mouse at (0,0) then translated to (mouseX, mouseY)... but the translated one is tinted with the last issued fill().
if there are no fill()'s issued, the bitmap is imaged just fine.
and if you are wondering why i need to use translate(), it is because i need to rotate the bitmaps that i am imaging along their axis, and the only way i know of doing that is imaging at the origin, using rotate() and the translate() to put them where they should be.
c
|
|
|
|
|
arielm
|
Re: why does fill() tint bitmap images?
« Reply #1 on: Sep 12th, 2003, 9:21pm » |
|
concerning bitmaps affected by the fill() color, it's not a bug, but rather by design...
so, fill() should always be set to white, if one wants to get a non-tinted picture.
|
Ariel Malka | www.chronotext.org
|
|
|
fry
|
Re: why does fill() tint bitmap images?
« Reply #2 on: Sep 13th, 2003, 9:00pm » |
|
that said, since this is confusing, we're adding tint() to the next release so that people don't get so confused by this.
|
|
|
|
|
trip
|
Re: why does fill() tint bitmap images?
« Reply #3 on: Sep 13th, 2003, 11:26pm » |
|
thanks, that works... and it is confusing, especially since fill() does not that way if translate() is not called.
anyway, thanks
c
|
|
|
|
|
fry
|
Re: why does fill() tint bitmap images?
« Reply #4 on: Sep 14th, 2003, 8:25pm » |
|
yup, that part would be a bug 
|
|
|
|
|
|
