Re: Python/SWIG handling of pointers to an image buffer
I think the jet lag is getting to me ;)
The answer to my question is that GetImageBuffer() is in the Camera device API but not the core API. The methods that return images in the Core API all return void pointers, so the Python wrapper really is converting the return types of popNextImage(), getLastImage(), etc. correctly; SWIG is not automatically converting unsigned char*'s to void*'s.
I still don't know why the Java wrapper defines a typemap(out) for unsigned char*'s since no core API method returns a pointer to this datatype, but I am willing to live with this little mystery.