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

[John W. Eaton]

Update of bug #30784 (project octave):

                  Status:                    None => Fixed                  
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #3:

I think we need to use a vector because an Octave image can contain multiple
frames.  As I understand it each frame is considered a separate image in the
vector that is passed to the writeImages function.

Your change seems to solve the reported problem so I checked it in.

Unfortunately, if you try

  imwrite (img, "foo.jpg", "tif")

the file is written in JPEG format, not TIFF even though we are setting the
type to "tif" before calling writeImages.  Ugh.  This "feature" is a bit
annoying, as I think the contents of a file should determine what is in it,
not the filename extension. I don't suppose this is a big problem because not
many people are likely to want to mix things up this way.  But what if I don't
know about all the naming conventions and I have some other reason to use
.jpg, like maybe it stands for "John's Perfect Graph".  Who cares if I want to
write TIFF data to a file with a .jpg extension?

Also, in the future, it would be helpful if you sent Mercurial changesets
instead of plain diffs.

Thanks.

    _______________________________________________________

Reply to this item at:

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

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