To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102119
------- Additional comments from m...@openoffice.org Thu Jun 11 09:39:25 +0000 2009 ------- OOo internal scripting isn't an issue, as we can easily add code that automatically invalidates the slot states (or triggers the clipboard notification) when something in OOo is put into clipboard (via UI or API doesn't matter). This leaves the case of external scripting, means: running a script in an external application that changes the content of the clipboard while an OOo window has the focus. I consider this case as esoteric enough to ignore it for the time being. If we don't want to ignore it in the long run, we can still implement the clipboard notification, but this shouldn't block this issue from being fixed for 3.2. What do you both think? --------------------------------------------------------------------- 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: issues-unsubscr...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
