Bug 46383 - Autocorrect: Correct accidental use of cAPS LOCK key isn't working
Summary: Autocorrect: Correct accidental use of cAPS LOCK key isn't working
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Master old -3.6
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-21 03:24 UTC by Thomas Arnhold
Modified: 2021-01-29 15:30 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Arnhold 2012-02-21 03:24:57 UTC
The autocorrect feature "Correct accidental use of cAPS LOCK key" isn't working. I checked it on Linux (SAL_USE_VCLPLUGIN gtk and gen) and Windows.

Here's some entry point to the code:

http://opengrok.libreoffice.org/xref/core/editeng/source/misc/svxacorr.cxx#1387

There's a reference to SimulateKeyPress() which is only really implemented as SalDisplay::SimulateKeyPress() and WinSalFrame::SimulateKeyPress(). All other implementations are empty methods. Maybe this is a hint, but I'm tapping in the dark, because this would mean it has to work at least on Windows...
Comment 1 sasha.libreoffice 2012-05-23 02:37:14 UTC
Thanks for bugreport
In 3.5.3 on Fedora 64 bit it works. May be fixed?
Comment 2 Thomas Arnhold 2012-05-27 06:11:38 UTC
I tested it with 3.4.3 on ArchLinux 32 bit. Doesn't work.

Maybe I don't get this feature? I type some text, hit accidentally the caps key, and type ahead. In my understanding the Autocorrection should keep track of this, but it doesn't.
Comment 3 sasha.libreoffice 2012-05-28 01:15:27 UTC
Thanks for additional testing. Please, test also in 3.5.4 when it appears.
Comment 4 Thomas Arnhold 2012-06-03 14:03:57 UTC
Appears also in 3.5.4 and master 27cd9157ac0e824197aa40c67fe6a4bfab3b2e38
Comment 5 Thomas Arnhold 2012-06-03 14:17:54 UTC
Doesn't work on Windows with 3.5.4 too (didn't test earlier versions).

PS: I don't mean the option "Correct TWo INitial CApitals"!
Comment 6 sasha.libreoffice 2012-06-04 00:27:30 UTC
Not reproduced in 3.5.4 on Windows and Linux in Writer and Calc (other not tested)
I enable CapsLock on keyboard and type aSDF. When I press space, CapsLock disables automatically and aSDF transforms to Asdf.
Comment 7 Thomas Arnhold 2012-06-04 06:43:28 UTC
Maybe I don't get it. I did as you did, but it won't disable automatically. Tested with Gnome 3.2, Xfce 4 on Linux and on a laptop with Windows 7. For both cases it won't work.

I tested the German and English (us) Interface. Both machines are 32 bit.

How fast do you type? What is your interface language?
Comment 8 sasha.libreoffice 2012-06-04 23:18:12 UTC
LO UI language used English and Russian. Typing speed as usually, tried faster and slower - not depends.

Tools->Autocorrect Options->tab "Option"->"Correct accidental use of cAPS LOCK key" enabled

Works correctly also on Windows 7 in 3.5.2 without JRE

May be in LO user profile is something wrong? What if move it to another place for experiment with fresh profile?
Comment 9 Thomas Arnhold 2012-06-05 00:36:30 UTC
Yes, did this with fresh profiles. Can anybody else check this?!
Comment 10 sasha.libreoffice 2012-06-05 01:03:24 UTC
@ Rainer
Greetings
Please, help us with reproducing this bug
Comment 11 Rainer Bielefeld Retired 2012-07-31 15:15:45 UTC
NOT reproducible with Server Installation of  "LibreOffice 3.6.0.4 rc  English UI/ German Locale [Build-ID:  932b512] on German WIN7 Home Premium (64bit) as long as I suffer from the "because of damaged budled Extensions in user profile not dictionaries available". Different to "Autocorrection TWo INitial CApitals" problem (?) this is independent to "dictionaries not available" bug.
Comment 12 tommy27 2012-12-28 23:59:40 UTC
(In reply to comment #6)
> Not reproduced in 3.5.4 on Windows and Linux in Writer and Calc (other not
> tested)
> I enable CapsLock on keyboard and type aSDF. When I press space, CapsLock
> disables automatically and aSDF transforms to Asdf.

did the same test as sasha on Windows VIsta 64 bit
NOT reproducible with LibO 3.6.4 and LibO 4.0 beta2+

since I'm the 3rd user not confirming this bug I'm gonna change status as RESOLVED WORKSFORME
Comment 13 Thomas Arnhold 2013-01-03 14:02:40 UTC
Ok. I did have a look at this. I found the solution: aSDF would be corrected to Asdf as it should be. But I tried asDF and expected to be corrected to Asdf. But that's not the point of this autocorrect feature. It corrects the mis-use of caps-lock in a case where caps was assumed key. Thanks for your help!