[Top][All Lists]

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

[Octave-bug-tracker] [bug #51203] xlswrite(...'com') output results in a

From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #51203] xlswrite(...'com') output results in a corrupted .xlsx / unicode issues
Date: Sun, 9 Jul 2017 16:05:11 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46

Follow-up Comment #61, bug #51203 (project octave):


Only the OCT interface invokes "cd" explicitly.

If you look in the test functions
you'll note many pause statements for most if not all interfaces. All of those
were needed to circumvent errors due to the OS apparently not being ready for
the next command in those scripts.

Setting the value of "dly" (the delay time) to zero will help to illustrate
where the errors exactly occur for which interface.

Results on your computer(s) would be interesting.
I was thinking that the "while strcmpi (pwd, ..)" loop could be morphed into a
piece of code that assesses a machine-specific required delay time for each
machine it runs on at the start of each first invocation of xlsopen or
xlsclose, using persistent or global variables. That while loop may need to
exit after the total accumulated delay would reach a max. of 1 second or so to
avoid a hang.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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