octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #58942] [octave forge] (io) version 2.6.1 read


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #58942] [octave forge] (io) version 2.6.1 read cell range data from worksheet
Date: Thu, 13 Aug 2020 14:35:06 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0

Update of bug #58942 (project octave):

                  Status:         Patch Submitted => Need Info              

    _______________________________________________________

Follow-up Comment #2:

Thanks Carlos for your patch.

I'm unsure what issue your patch is meant to solve. Can you explain, please?
Can you also tell us which io package version you use?
just do "pkg list io" and you get something like this:

>> pkg list io
Package Name  | Version | Installation directory
--------------+---------+-----------------------
          io *|   2.6.2 | ... <some long path name> ...


where (in this exaample) 2.6.2 is the io package version.

The error message you mention comes from private function  __OCT_xlsx2oct__.m 
which will only be invoked when using the OCT spreadsheet I/O interface.
However your patch would apply for all interfaces. I'm not sure if that is a
good idea.

That said, that error message exists for a reason. It simply says that if you
want to read from e.g., the 4th worksheet while there are only 3 worksheets in
the file, you want to do something impossible.
I don't see how that relates to the magic you want to apply to xls2oct.m's
input arguments.

Furthermore, you give an example using xlsread.m showing a range as second
argument rather than a worksheet. But that very logic has been there in
xlsread.m from the beginning in around 2009 (have a look at xlsread.m L.271
and up).
If that doesn't work for you out of the box I'd be very happy if you could
supply an example that shows the error.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?58942>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]