But how to see them if J crashes first? I could see that S_OK was zero in olecreate, but debug then only got as far as the first line oleinvoke with no chance of checking the code.
Bill was keen to see reports on wdooo behaviour with a variety of Windows o/s and numbers of bits. Mike On 06/11/2014 13:37, bill lam wrote:
When calls in wdooo fail, they should return non-zero error code,that might give hints of why it failed. On Nov 6, 2014 5:05 PM, "Mike Day" <[email protected]> wrote:Dear Forum I've got a problem with J crashing with wdooo, which I've been discussing privately with Bill Lam. Privately because my example involved private data. We seem to have discovered where the trouble lies or at least where it starts, and in a public area, so it can be shared. I tried the verb "test" in ~addons/tables/wdooo/oocalc.ijs. Using debug, I see that it fails at the line olemethod__p base ; 'createInstance' ; 'com.sun.star.frame.Desktop' (Actually, olemethod attempts to call oleinvoke; the error appears to occur with '' (m oleinvoke) y ) Executing this line throws an exception under Windows 8.1 with the message jqt.exe has stopped working etc While I'm running Apache Open Office 4.1.1 in Windows 8.1 on a 64 bit machine, Bill has libreoffice 4.3.3 in windows xp in 32 bits, where oocalc's test works ok, so we're at an impasse. Is anyone else who's got an Open Office + 64-bit Windows 8.1 setup willing to try the oocalc test? I recall trying out libreoffice two or three years ago and then finding Open Office to be more stable - but perhaps things have improved. Thanks in advance, Mike
--- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4765 / Virus Database: 4189/8520 - Release Date: 11/06/14 ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
