SDL_image 1.2.11 RELEASED!

This is a bugfix release for SDL_image:
http://www.libsdl.org/projects/SDL_image/

CHANGES:

Thanks to these people and many others for their help on this release:
Mark Tucker, Thomas Klausner, Michael Bonfils

See ya!–
-Sam Lantinga

On this fix “Fixed loading 8-bit PNG images on Mac OS X” did it require
initialization prior to the call and therefore work on the second call and
not the first in some cases? I remember a guy who had an issue with that
and it seems like that was his answer.
I’m sorry to ask but I looked around and didn’t see any listing of details
of what code fixed the issue and what the issue of origin was. It’s helpful
to see what complaint drives the discovery of the bug and then ultimately
why it didn’t work and how the code needed to change in order to bring
about the fix. If There is a listing of that where is it? I suppose for the
code change part I should compare the versions side by side but often
enough there are parts of it I don’t understand.On Sun, Jan 15, 2012 at 6:23 PM, Sam Lantinga wrote:

This is a bugfix release for SDL_image:
http://www.libsdl.org/projects/SDL_image/

CHANGES:

Thanks to these people and many others for their help on this release:
Mark Tucker, Thomas Klausner, Michael Bonfils

See ya!

-Sam Lantinga


SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

Hello !

On this fix “Fixed loading 8-bit PNG images on Mac OS X” did it require
initialization prior to the call and therefore work on the second call and
not the first in some cases? I remember a guy who had an issue with that
and it seems like that was his answer.
I’m sorry to ask but I looked around and didn’t see any listing of details
of what code fixed the issue and what the issue of origin was.

The easiest way to look, what code has been commited to SDL_image/SDL_mixer/… to do/fix what,
is to look at the commit logs :

http://hg.libsdl.org/SDL_image/log/8ad1188058fb

Sam/Ryan/… always write in the commit message a what/why/how,
like the original email from the patch author or a bugzilla number.

CU