To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=95038





------- Additional comments from [email protected] Sun Oct  4 08:41:51 
+0000 2009 -------
@rainerbielefeld: I'm not inactive I spend long time searching your bug reports
a year ago, I found one where the clipboard issue was discussed and it seemed
they found the probable cause of the problem. Using comodo I started to
understand where the problem is. The OO has probably created global hook to the
clipboard on windows and everytime any program places anything into the
clipboard OO is accessing this information. Thanks to comodo I can block this
access so it does not effect any other application. And I've got a feeling that
I haven't experienced the problem. Unfortunately I do not remember the number of
that issue where it was discussed, just remember the last thing that was said.
Something like this: "The problem seems to be in clipboard library, but no one
wants touch it, because it is somehow old and complicated and it would require a
lot of testing". It was something in this sens. I think I signed on that issue
too and haven't got any email since then. All together I have found 4 or 5
similar issues all corresponding the same clipboard problem. Truth is that now
I'm using vista and soon I will move to win7 so the behavior has changed
completely. If I'll have time I'll try to reproduce the problem on my new 
laptop. 

---------------------------------------------------------------------
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]

Reply via email to