Issue 1342 - Autofill overworked
Summary: Autofill overworked
Status: ACCEPTED
Alias: None
Product: Calc
Classification: Application
Component: code (show other issues)
Version: 633
Hardware: PC Windows NT
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
: 2014 (view as issue list)
Depends on:
Blocks:
 
Reported: 2001-07-26 23:15 UTC by issues@www
Modified: 2013-08-07 15:12 UTC (History)
4 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Here's the file (6.57 KB, application/octet-stream)
2003-12-06 14:52 UTC, issues@www
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description issues@www 2001-07-26 23:15:22 UTC
Check out the submitted file. Try to change the "tyPo" to "typo".
Comment 1 issues@www 2001-07-26 23:16:07 UTC
Created attachment 428 [details]
Here's the file
Comment 2 peter.junge 2001-07-27 09:59:48 UTC
Hi,

I can reproduce this one. Beginnig 'Fix typo with a single quote helps. But I
also think that autofill goes to far in this case.
Rgds., Peter
Comment 3 niklas.nebel 2001-07-27 20:12:53 UTC
Changing the case of the input to that of existing column entries is a useful 
feature that I don't want to remove. It is part of AutoInput, so if you turn 
that off, you can enter text in the "wrong" case. Unless you have a suggestion 
how to please everybody, I'll have to reject this.
Comment 4 issues@www 2001-07-27 20:35:14 UTC
I was just playing with Excel. They seem to handle both cases pretty well. Rules
for "tyPo":

1. If you type "t", "ty", or "typ" in any case it will autofill to "tyPo".
2. If you type "typo", "Typo", or "TYpo"...etc. it will keep as you typed it.
This makes sense since why would you use autofill if you're going to type it all
in?
3. If you go back and edit "tyPo" to "tyPO" etc. it will keep you edits.

Note: I'm not the only person that noticed this problem, see:

http://www.openoffice.org/www-discuss/current/msg04705.html

-Sep
Comment 5 peter.junge 2001-12-07 12:50:32 UTC
The latest comments of Niklas and Sepehr are leading me to the
conclusion that this is an feature wish.
Regards, Peter
Comment 6 peter.junge 2001-12-07 12:51:42 UTC
to Falko
Comment 7 falko.tesch 2002-01-02 10:45:16 UTC
This issue is re-assigned to Christian Jansen for further evaluation.
Comment 8 christian.jansen 2002-01-02 14:08:10 UTC
I have to agree to Sepehr and Peter, we should give users an easy
solution to correct typos. This issue is also important for
accessibility. 
Comment 9 christian.jansen 2002-01-14 09:56:40 UTC
*** Issue 2014 has been marked as a duplicate of this issue. ***
Comment 10 christian.jansen 2005-05-20 15:08:08 UTC
Reopened
Comment 11 christian.jansen 2005-05-20 15:08:43 UTC
Changed state to accepted
Comment 12 clement_pillias 2009-02-11 18:40:02 UTC
This issue should:
- title changed to 'Improve the way AutoInput deals with capitalization in Calc'
- have 'platform' field set to 'All'
- some milestone set?
Comment 13 jcrandall 2011-08-22 23:36:44 UTC
Regardless of what the AutoInput settings are, if the user responds to an unwanted AutoInput by immediately retyping the cell contents the same way again, AutoInput should not modify the input the second time around. 

It seems that Excel disables all of its autocorrection if the user retypes the same thing twice, and many other text input UIs behave in a similar way (such as the iPhone and other mobile devices).  It is extremely frustrating to users to not allow them to type the cell contents the way they want to, especially if they repeatedly enter the same information. It would seem to be an easy addition to add the capability to detect the user's "insistence" that they meant what they said. If the user insists, AutoInput should back down and not change case of what the user has typed.

It seems like this would only very slightly complicate the code by needing to have a way to store the last input that AutoInput responded to and compare that against the current entry, but it seems like that should be fairly easy to implement and that should definitely be the default behavior.