To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=63270
------- Additional comments from [EMAIL PROTECTED] Fri Mar 17 07:24:44 -0800 2006 ------- sw->thoriredd: I try to understand the behaviour ... maybe my brain doesn't work properly at the moment ;-) ... originally you had xModifiable.setModified(false); xComponent.dispose(); and sometimes your program stopped at the first call and you had to kill the office manually which will no doubt raise a DisposedException in the dispose() call because the office is gone. Now you only have xCloseable.close(true) what happens now ... does it sometimes freeze in this call and you have to kill the office manually followed by the DisposedException ... or do you always get a DisposedException when calling close(true) now ? --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
