| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
This allows the library header to have a name consistent with
the library soname.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There is no difference in what the client needs to do.
If there are displayable frames, they can display them.
Otherwise more data is needed.
Internally only `GIF_INSUFFICIENT_DATA` is used now.
To remove the `GIF_INSUFFICIENT_FRAME_DATA` could make existing
client applications fail to compile, so it is left as an alias
to the same value.
At some point the API will be changed drastically, but for now
I want existing applications to still build.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
If the frame has no transparency, it is set to an invalid value.
|
|
|
|
|
|
|
|
|
|
|
| |
We used to memset a colour we looked up in the colour table when
clearing the previous frame. This didn't make sense, because the
colour is four bytes wide. Now we write the actual colour in
properly.
Also, the background color comes from the global colour table
(if one exists), rather than from the local colour table. If
there is no colour table, black is used.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Previously we decoded a previous frame over the current frame data
to handle resoration. However, the previous frame depended on its
own previous frame state for correct decode.
Now we just make a copy of the previous frame data and copy it
back to handle the GIF_FRAME_RESTORE case.
See: https://github.com/libvips/libvips/issues/1084#issuecomment-653497200
|
| |
|
| |
|
| |
|
|
|
|
| |
svn path=/trunk/libnsgif/; revision=10949
|
|
svn path=/trunk/libnsgif/; revision=6983
|