[Octave-bug-tracker] [bug #30784] imwrite fails when FMT is set explicitly

[John Swensen]

Follow-up Comment #2, bug #30784 (project octave):

I think something like the following should solve your problem (BTW, I am not
an ImageMagick expert, but did a simple test using one of their examples).

In the write_image function of __magick_read__.cc, we use the STL compatible
Magick::WriteImages () function.  I don't think this is necessary.  Correct me
if I am wrong, but doesn't the variable 'img' always get passed in a single
image?  If this is the case, then I think we can do the following:

1) Fix the start of the function so that the octave_value 'img' is encoded
properly and placed in an instance of Magick::Image called 'image' (i.e. get
rid of the STL::vector).
2) Execute the following commands: 
         image.magick(fmt);    // fmt as passed in as string to the
write_image function
         image.fileName(filename);   // filename as passed in as string to
the write_image function
         WriteImage( image.imageInfo(), image.image() );  // This is a call
to the C ImageMagick library with calls to the proper ImageMagick++ member
functions of ImageMagick::Image to retrieve the C structures necessary to
satisfy the parameter list

Hope this helps.  I don't currently have a working build on my OSX system
(still fighting with gfortran issues) or I would make and test a patch myself.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?30784>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/