In article <
59f8607...@sprie.nl>,
Paul Sprangers <
Pa...@sprie.nl> wrote:
To answer my own questions:
> Is that one sprite area for both sprite files, or should both files have
> their own area?
A bit of experimenting shows that one sprite area should do.
> And is it really OS_SpriteOp 9 - 12, or should I add 256 to those
> numbers? (That's what the StrongHelp manual suggests).
Another bit of experimenting shows that 256 should indeed be added to the
original reason code.
Some of the sprites that I merged to the sprite area have overwritten the
original one as intended, but a lot of others delete all sprites in the
sprite area, after which the file consists of the new sprite only. And I've
no idea where that comes from. Here is my code:
$spritepath% = path$
SYS "OS_SpriteOp, 265+11, sparea%, spritepath%
SYS "OS_SpriteOp, 256+12, sparea%, originalpath$
- spritepath% contains the path of the sprite to be merged.
- sparea% is the sprite pool that contains the 60 sprites file.
- originalpath$ is the path of that 60 sprites file.
The sprite to be merged has the same name as its file name (both "player"),
which is the name of a sprite in the large sprite file too. The latter
should be replaced by the new sprite. Sometimes it does, but mostly the new
sprite replaces all sprites, as said.
The new sprite is never larger than approximately 3500 bytes, reason why I
add a sufficient 5000 bytes to the length of the sprite pool (sparea%).
So, what am I still doing wrong?
Paul
--
https://riscos.sprie.nl