Apache OpenOffice (AOO) Bugzilla – Issue 4446
changing case shifts text selection right
Last modified: 2003-09-08 16:56:16 UTC
This is really three bugs, but I think they are all related. The most obvious one comes in the (?new) command on the format menu Case/characters. Select a word: change it to upper case. Then, without moving the selection, change it to lower case again. This time, the first selected character will be untouched, but the selection will extend one further char to the right. With each successive swap from upper to lower case, the selection will move OnE ChArAcTeR to the fight, leaving an effect like that behind it. I noticed this because of the second bug, which is intermittent. But cutting (ctrl-X) and then pasting (ctrl-V) a paragraph of ordinary mostly lower case text I discovered that sometimes the inserted text emerges all in Title Case; selecting it and then choosing Format->Case/Characters has no effect whatever. Finally, writing a macro to change the case of a text selection reveals that quite often the charcasemap property simply is not changed when the selection is read directly from "oDocument.currentcontroller.getViewCursor()" whereas the _exact same code_ works when the selection is defined by moving the cursor to the start and end of the current word. I can't help feeling these are all related.
I have refined the second bug here. I may break it out into a new issue: advice would be appreciated. The key to reproducing the behaviour is to use coloured text. Change the font colour of a text selection. Cut and paste. When it is pasted, the font colour is normal, but all the words have been put in title case.
First, thinking things are connected is a good idea but taking the time to write three issues and cross-mentioning them within each description would ease the way, regardless if they melt into one or go three different paths. Problem 1 (moving selection when toggeling uppercase-lowercase): This is reproducible in Oo.org Build 642 but is OK in Build 643 (1.1 candidate) so it can be ignored from now on. Please write a new issue for Problem 2 if you can reproduce it in a newer version. Only based on Problem 3, this one will be reassigned to Christoph.
OK. Number one is certainly fixed in 643 here. I can't reproduce number two, either, on 643, which leaves number three. I'm happy to file separate reports for every bug in future. I did ask for guidance about this when I filed these ones, back in May :- )
Can you please attach a macro to reproduce the behavior of the last one of the three bugs.
Hello Andrew Brown, can you please attach a macro to reproduce the behavior of the last one of the three bugs. Thx, Christoph
Nope. I can't. I have just written, and will upload, a macro using both methods to get at the string. They both work. So it is all fixed and we can celebrate another triumph!
CN: Bug is not reproducible.
CN: could be cloased
*** Issue 13605 has been marked as a duplicate of this issue. ***
Hi, Since this one has been fixed a long time (since 643C) is there any chance the fix can be backported to the OOo 1.0.X stable series which what the submitter originally specified as the version the bug appeared in? If a patch or specific versions needed to fix these issues can be identified, I would be happy to attempt to backport them and get them into OOO_STABLE_1 in time for the next stable release (since that tree just reopened). Any hints appreciated. Thanks, Kevin