| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This hopefully fixes the regression that was recently introduced
where the cursor would be visible, but black, during cutscenes.
This was presumably because the color black in a mouse cursor no
longer necessarily means that it's transparent.
|
|
I had assumed that PAL_PIXELS contained the colors encoded in
native byte order, but looking again it appears that it's always
encoded as little-endian.
|
|
Before, cursor images were converted to 16 bpp, and anything that
was the same as the first color in PAL_PIXELS[] was made transparent.
Now, cursors images are drawn as 8 bpp with a cursor palette created
from PAL_PIXELS[]. This preserves all the black parts of the cursor
that weren't actually color index 0.
It would be nice if we only regenerated the cursor/palette when they
have actually changed, but that's for later.
|
|
glitches on the chimney, but the birds are ok!.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
variables, move some variables to FontManager
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
"Menu: after the fading, a button is moved by 1 or 2 pixels"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
AnimationManager
|
|
GOTOs
|
|
|
|
|
|
|
|
|
|
Before starting an "Swav" sound, check that its sound handle isn't
already used. If it is, stop it. When skipping a movie, it still
(incorrectly?) goes through the motions of playing the remaining
frames, including starting any movie sounds on the way.
This would cause us to lose the handle to the sound that was
currently playing in the "Swav" slot, and I *think* that's what
ended up confusing things. I'm still not entirely sure exactly
what was happening.
|
|
|
|
|
