ChangeFSI v1.27
Paul Vigay (85) 3 posts |
There appears to be a bug in ChangeFSI version 1.27 in that when you convert an image to a sprite and then save the resulting sprite to disc, the spritename within the resulting spritefile is different to previous versions of ChangeFSI. This causes a problem with external applications which have been written to use ChangeFSI for their image conversions. Previous versions called the file “p” followed by various numbers dependant upon the various options you’d got set in ChangeFSI. v1.27 appears to save the sprite with the spritename equal to the filename you’re converting. I’ve not had a chance to examine the source code yet, so I can’t offer a solution at this point, but I’ll see if I can have a nose later. |
Steve Revill (20) 1361 posts |
It was a deliberate change – it seemed more useful to generate a sprite with a name which matched the leaf name of the source image rather than some collection of stuff which is different depending upon what processing you apply. All the more so if you process a few images and each time want to drop them into a sprite file window but each new one would overwrite the last because it had the same name! If you have written code assuming the name of a sprite generated by ChangeFSI, I suggest you fix the code to use the appropriate OS_SpriteOp call to return the name of the first sprite in the file. That will work no matter what name the sprite has. If at some future date CFSI got some new processing options, these could’ve changed the sprite names it generated, too. |