[Octave-bug-tracker] [bug #29474] imread will not read graphics files

[John W. Eaton]

Follow-up Comment #12, bug #29474 (project octave):

Looking at the diffs between 3.2.3 and 3.2.4, I don't see any reason that
accounts for this difference.

Can anyone else confirm this behavior with the Windows binary?

Since I'm unable to reproduce this problem and I don't use Windows (or have
access to a Windows system suitable for debugging) someone else will have to
debug this problem.

As a workaround, I think you should be able to modify the imread function to
do

  fn = filename

instead of

  fn = file_in_path (IMAGE_PATH, filename);

Then it won't search IMAGE_PATH for the image file, but at least it should be
able to open the file if it can be found relative to the current directory or
if it is specified with an absolute filename.

    _______________________________________________________

Reply to this item at:

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

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