Apache OpenOffice (AOO) Bugzilla – Issue 49747
paste over selected words not updated visually
Last modified: 2017-05-20 11:15:49 UTC
Open up Writer. Type in the first line: 1 : - move at beat 4, and beat 8. Type in the second line: 1 move per beat Select the whole second line - ie move cursor to beginning of second line, and hit shift-end, then ctrl-c Select from the first line 'move' till end of line - ie move cursor to right before m in move, then click shift end. ('move at beat 4, and beat 8.' is selected) Paste by pressing ctrl-v The paste will not appear to be correct until you hit pg-dn so words are above screen, and then pg-up.
Created attachment 26488 [details] Described document content
MRU->FME: open attached document. Select whole second paragraph and copy to Clipboard. Select first paragraph from beginning of "move" to its end and paste Clipboard content -> view is not painted correctly; can be corrected manually by Ctrl-Shift-R
*** Issue 51479 has been marked as a duplicate of this issue. ***
Hm, currently (issue 51479) I am not so lucky with finding DUPs :-( Added keyword oooqa
Confirmed still present in m109 in WinXP.
*** Issue 53763 has been marked as a duplicate of this issue. ***
*** Issue 69683 has been marked as a duplicate of this issue. ***
*** Issue 71800 has been marked as a duplicate of this issue. ***
*** Issue 72097 has been marked as a duplicate of this issue. ***
*** Issue 84091 has been marked as a duplicate of this issue. ***
*** Issue 87486 has been marked as a duplicate of this issue. ***
*** Issue 70617 has been marked as a duplicate of this issue. ***
Dear developers, any chance to get this issue fixed any time soon? Thanks and regards, KP.
fme->kpalagin: Well, it's "only" a repaint issue, but I admit that this is somewhat annoying. Anyway, to be honest, I doubt that I have the time to take care of this soon. I hope you understand. Any volunteers for this?
*** Issue 97713 has been marked as a duplicate of this issue. ***
Please see issue 97713 for a simplest case of reliably reproducing this bug. This bug has been outstanding for FOUR years. It needs to be fixed in the next release of writer. The results are ugly and truly point to a product that is not being maintained in a professional way. This error is so annoying that had I seen this bug early on with writer, I would not have adopted OpenOffice as my choice of software. The priority should be raised from P3 to P2.
@mru - I'm really sorry I cannot contribute to OOo as I have many, many years of development experience. But I'm retired from the mêlée of development now and quite honestly don't want to dump myself into the cauldron again. In my over thirty years of experience development resources have *always* been limited ... because they are expensive. But our QA teams have always been unrelenting on product quality and any reliably repeatable bug was required to be fixed before any release went forth. In fact, all future development will be stopped ... even at Microsoft ... and resources turned on these problems until they are gone. All "we'll fix in the future" and "nice to have" issues are either DROPPED if unneeded or advanced in priority after every release if required ... so level 3 problems become level 2 problems and level 2 problems become level 1 problems if the development team is not doing its job of getting them solved. Even though these bugs kept me at work for many hours ... they did get addressed ... because management insisted that it was so ... and almost all of them wasn't even my code, but the team's code ... because of the different skill levels of the programmers. I'm sorry that resources are slim ... but as I say ... who needs new features when the existing code is laden with bugs? Adding new code only increases the population of bugs. And I disagree with fme's assessment ... a repaint problem is not a trivial bug in a WYSIWYG editor. When garbage appears on the screen and the user is spending time cleaning up his own document, he doesn't need the editor to be placing its garbage there as well. It becomes a lot of time chasing ghosts. And every new person identifying an existing bug over a period of four years ... and the time involved in isolating and creating a minimal test case and taking time to submit the bug and the development team re-identifying it as a duplicate over FOUR years is not a good use of either the customer's or the developer's time. I nevertheless thank everyone for bringing this wonderful product to open development.
I'm seeing this on OS X 10.6.2 with ooo 3.1.1 as well. It's a pretty bad bug userwise. Makes you lose confidence in the software.
Sigh ... this is still outstanding over one year past the comment: 'Well, it's "only" a repaint issue' I thought comments like this only came from Microsoft. Having worked for them ... you can take my word for that! And like was just mentioned: "It's a pretty bad bug userwise." WYSIWYG ... more like WYSINWYG!
I am taking over this issue and adjusting its target - I hope to fix it in one of the next releases.
;-) forgot to assign to myself
*** Issue 116622 has been marked as a duplicate of this issue. ***
Reset assigne to the default "issues@openoffice.apache.org".