[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Octave 3.4.3 for Mingw; IMRead
From: |
ijourneaux |
Subject: |
Re: Octave 3.4.3 for Mingw; IMRead |
Date: |
Tue, 14 Feb 2012 12:43:41 -0800 (PST) |
PhilipNienhuis wrote
>
> <....so it seems the second parameter to imread should be a number
> (integer) pointing to some figure index in the image file container (I
> suppose for something like animated gifs that contain multiple images; or
> maybe even movies, to read a specific frame).
>
> If you want you can report this bug in the tracker, i.e. that the
> documentation of imread.m is inadequate and the error message you get is
> confusing because of the incomplete help text.
> Better yet, post a fixed help text with it (it isn't hard, just look at
> imread.m's help text).
>
I have reported it as a bug in the bug tracker as it use to work under
3.2.4. The Matlab defintion of imread is
A = imread(filename, fmt)
where the text string fmt specifies the format of the file by its standard
file extension. For example, specify 'gif' for Graphics Interchange Format
files. To see a list of supported formats, with their file extensions, use
the imformats function. If imread cannot find a file named filename, it
looks for a file named filename.fmt.
The definition of __magick_read__ hasn't changed since 3.2.4 but the
behavior has.
--
View this message in context:
http://octave.1599824.n4.nabble.com/Octave-3-4-3-for-Mingw-IMRead-tp4175118p4388480.html
Sent from the Octave - General mailing list archive at Nabble.com.