Apache OpenOffice (AOO) Bugzilla – Issue 19539
When drag&drop a 3d-clip to the writer: Windows: grapgic problems, Linux: OpenOffice closes itselfe
Last modified: 2004-05-06 11:49:17 UTC
Hello, Using the german OpenOffice 1.1RC (the most recent one in german language) with WindowsXP I found following bug: When drag&drop(!) one of these 3D-pics coming with the OpenOffice-installer into the the main-window of the writer and then move this object with the mouse, OpenOffice draws extreme graphic errors and must be re-started. I have attached 2 screenshots where you can see the problem. (I could reproduce the same problem with the last windows-final of StarOffice, bevore I switched to OpenOffice.) I found that the most recent german linux version does close itselfe instead of producing graphic-errors when doing like described above. I will try to attach screenshots to this issue that show this probolem.
Created attachment 9287 [details] Screenshots showing the problem with the Windows-version.
Created attachment 9288 [details] 2 Screenshots in a ZIP-archive
I found that it does not happen on another WindowsXP-computer. So it could be caused by special display-drivers or something similar... But I found under WIndows95 that moving such 3D-objects in general makes the writer unstable. Please check if it is a bug of OpenOffice, or not!
The graphic-problem does not happen when adding a copy by right- click instead of drag&drop. So I think it seams to be a problem of OpenOffice...
i can not reproduce this here, i will install the german version to verify if this is a german only bug. please can you tell me wich graphic adapter you got and the installed driver version? reassigned to jw
can not reproduce this in the german version too set to WFM
Now I have a new PC and I cannot reproduce the problem with it. So I think it is OK that this issue is closed.
setz to closed due the last comment of the issue reporter
I also had graphic problems with another program with the old PC, that I now cannot reproduce anymore. So I'm sure now, that it was a video-driver problem.