[devel] Fixed incorrect examples of callback prototypes in the manual.
"png_ptr ptr" should be "png_structp png_ptr"
This commit is contained in:
parent
135d17ce3e
commit
81ce889435
1
ANNOUNCE
1
ANNOUNCE
@ -97,6 +97,7 @@ Version 1.5.1beta09 [January 24, 2011]
|
||||
converting RGB to gray.
|
||||
|
||||
Version 1.5.1beta10 [January 24, 2011]
|
||||
Fixed incorrect examples of callback prototypes in the manual.
|
||||
|
||||
Send comments/corrections/commendations to png-mng-implement at lists.sf.net:
|
||||
(subscription required; visit
|
||||
|
1
CHANGES
1
CHANGES
@ -3213,6 +3213,7 @@ Version 1.5.1beta09 [January 24, 2011]
|
||||
converting RGB to gray.
|
||||
|
||||
Version 1.5.1beta10 [January 24, 2011]
|
||||
Fixed incorrect examples of callback prototypes in the manual.
|
||||
|
||||
In addition the order of the png_get_uint macros with respect to the relevant
|
||||
function definitions has been reversed. This helps the preprocessing of the
|
||||
|
@ -455,7 +455,7 @@ Setting up callback code
|
||||
You can set up a callback function to handle any unknown chunks in the
|
||||
input stream. You must supply the function
|
||||
|
||||
read_chunk_callback(png_ptr ptr,
|
||||
read_chunk_callback(png_structp png_ptr,
|
||||
png_unknown_chunkp chunk);
|
||||
{
|
||||
/* The unknown chunk structure contains your
|
||||
@ -501,8 +501,8 @@ called after each row has been read, which you can use to control
|
||||
a progress meter or the like. It's demonstrated in pngtest.c.
|
||||
You must supply a function
|
||||
|
||||
void read_row_callback(png_ptr ptr, png_uint_32 row,
|
||||
int pass);
|
||||
void read_row_callback(png_structp png_ptr,
|
||||
png_uint_32 row, int pass);
|
||||
{
|
||||
/* put your code here */
|
||||
}
|
||||
@ -1507,7 +1507,7 @@ with
|
||||
|
||||
You must supply the function
|
||||
|
||||
void read_transform_fn(png_ptr ptr, row_info_ptr
|
||||
void read_transform_fn(png_structp png_ptr, row_info_ptr
|
||||
row_info, png_bytep data)
|
||||
|
||||
See pngtest.c for a working example. Your function will be called
|
||||
@ -2167,7 +2167,7 @@ called after each row has been written, which you can use to control
|
||||
a progress meter or the like. It's demonstrated in pngtest.c.
|
||||
You must supply a function
|
||||
|
||||
void write_row_callback(png_ptr, png_uint_32 row,
|
||||
void write_row_callback(png_structp png_ptr, png_uint_32 row,
|
||||
int pass);
|
||||
{
|
||||
/* put your code here */
|
||||
@ -2772,8 +2772,8 @@ with
|
||||
|
||||
You must supply the function
|
||||
|
||||
void write_transform_fn(png_ptr ptr, row_info_ptr
|
||||
row_info, png_bytep data)
|
||||
void write_transform_fn(png_structp png_ptr ptr,
|
||||
row_info_ptr row_info, png_bytep data)
|
||||
|
||||
See pngtest.c for a working example. Your function will be called
|
||||
before any of the other transformations are processed. If supported
|
||||
|
14
libpng.3
14
libpng.3
@ -1374,7 +1374,7 @@ Choices for (int) ancil_action are
|
||||
You can set up a callback function to handle any unknown chunks in the
|
||||
input stream. You must supply the function
|
||||
|
||||
read_chunk_callback(png_ptr ptr,
|
||||
read_chunk_callback(png_structp png_ptr,
|
||||
png_unknown_chunkp chunk);
|
||||
{
|
||||
/* The unknown chunk structure contains your
|
||||
@ -1420,8 +1420,8 @@ called after each row has been read, which you can use to control
|
||||
a progress meter or the like. It's demonstrated in pngtest.c.
|
||||
You must supply a function
|
||||
|
||||
void read_row_callback(png_ptr ptr, png_uint_32 row,
|
||||
int pass);
|
||||
void read_row_callback(png_structp png_ptr,
|
||||
png_uint_32 row, int pass);
|
||||
{
|
||||
/* put your code here */
|
||||
}
|
||||
@ -2426,7 +2426,7 @@ with
|
||||
|
||||
You must supply the function
|
||||
|
||||
void read_transform_fn(png_ptr ptr, row_info_ptr
|
||||
void read_transform_fn(png_structp png_ptr, row_info_ptr
|
||||
row_info, png_bytep data)
|
||||
|
||||
See pngtest.c for a working example. Your function will be called
|
||||
@ -3086,7 +3086,7 @@ called after each row has been written, which you can use to control
|
||||
a progress meter or the like. It's demonstrated in pngtest.c.
|
||||
You must supply a function
|
||||
|
||||
void write_row_callback(png_ptr, png_uint_32 row,
|
||||
void write_row_callback(png_structp png_ptr, png_uint_32 row,
|
||||
int pass);
|
||||
{
|
||||
/* put your code here */
|
||||
@ -3691,8 +3691,8 @@ with
|
||||
|
||||
You must supply the function
|
||||
|
||||
void write_transform_fn(png_ptr ptr, row_info_ptr
|
||||
row_info, png_bytep data)
|
||||
void write_transform_fn(png_structp png_ptr ptr,
|
||||
row_info_ptr row_info, png_bytep data)
|
||||
|
||||
See pngtest.c for a working example. Your function will be called
|
||||
before any of the other transformations are processed. If supported
|
||||
|
Loading…
Reference in New Issue
Block a user