To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=64555
User cd changed the following:
What |Old value |New value
================================================================================
Status|NEW |STARTED
--------------------------------------------------------------------------------
Issue type|DEFECT |PATCH
--------------------------------------------------------------------------------
Target milestone|OOo 2.x |OOo 2.2.1
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Tue Jan 9 06:56:55 -0800
2007 -------
cd->beppec56: Thanks for your patch. I checked it and I think you use an
implementation detail (SFX_CALLMODE_RECORD) to distinguish between called from
API and UI. I am not sure that it always works, but you shouldn't do it. The
dispatch API is defined to be used by the user interface and therefore the
implementation should use UI as necessary. Only the normal OpenOffice.org API is
not allowed to use UI. I can accept the other part, which implements the PDF
options dialog. I don't know if you want to provide a cleaned up patch or should
I adapt your code to not use the "scripting" detection?
---------------------------------------------------------------------
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]
