PixelGetNextPixel

The MagickWand interface is a new high-level C API interface to ImageMagick core methods. We discourage the use of the core methods and encourage the use of this API instead. Post MagickWand questions, bug reports, and suggestions to this forum.
Post Reply
*void

PixelGetNextPixel

Post by *void » 2006-12-25T17:33:14-07:00

The description of PixelResetIterator in pixel-iterator.html says:
"PixelResetIterator() resets the pixel iterator. Use it in conjunction with PixelGetNextPixel() to iterate over all the pixels in a pixel container."

PixelGetNextPixel is not in the DLL and is not in any of the headers. A Google search reveals only the mention in pixel-iterator.html. Seems a dead end.

Could this mean PixelGetNextRow? Which (according to the header it is prototyped in) is also deprecated.

Trying to set up to use the DLL with a different programming language. Many of the function descriptions are pretty cryptic making slow going.

User avatar
magick
Site Admin
Posts: 10922
Joined: 2003-05-31T11:32:55-07:00

Post by magick » 2006-12-25T19:02:22-07:00

Will fix the documentation. In the mean-time use PixelGetNextIteratorRow(). See the source distribution for wandtest.c which has a few examples of using the MagickWand API.

*void

Post by *void » 2006-12-26T16:33:30-07:00

Thanks for the explanation.

I am prototyping the MagickWand interface for use with a language other than C. My main source of reference is the set of API html files. (Backed up by the header files when I can't seem to make sense of the web doc. )

I am running across quite a few other clinkers in the doc. Most of which are relatively easy to puzzle out with the help of the headers. What would be the most appropriate way to report the errors? (And maybe some suggestions on improvements in the descriptions. :) )

User avatar
magick
Site Admin
Posts: 10922
Joined: 2003-05-31T11:32:55-07:00

Post by magick » 2006-12-26T16:38:19-07:00

The best path foward would be to document all the problems in a file and send us a private message. We'll make sure all your suggestions make it back into the documentation so others can benefit from your effort.

Post Reply