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

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

[Octave-bug-tracker] [bug #55823] [octave forge] (io) xlsread(...) call


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #55823] [octave forge] (io) xlsread(...) call using OCT interface interferes with GUI editor
Date: Thu, 7 Mar 2019 18:02:47 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48

Update of bug #55823 (project octave):

              Item Group:             Performance => Unexpected Error       
                  Status:               Need Info => Confirmed              
             Assigned to:                    None => philipnienhuis         
                 Release:                   5.1.0 => dev                    
                 Summary: [octave forge] (io) xlsread(...) call interferes
with Octave editor GUI => [octave forge] (io) xlsread(...) call using OCT
interface interferes with GUI editor

    _______________________________________________________

Follow-up Comment #4:

Confirmed on Windows 10 with Octave-6.0.0(dev version)

This is really an intriguing one ... I have no idea what is going on.

I opened your file readtest.m in the Octave editor, changed the command 
xlsread('test.xlsx') 
into 
xlsread('test.xlsx', 1, '', 'oct')
selected it using the mouse cursor and pressed F9
Then I got a popup that h file was changed and if I wanted to save the
changes, which indicates the editor wants to close the file.

It is only with the (native) OCT interface that it happens. With COM (using
MS-Excel behind the scenes) I can't reproduce it.


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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