Issue 4333 - auto-save causes discarded keystrokes [v. 641d]
Summary: auto-save causes discarded keystrokes [v. 641d]
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: 641
Hardware: PC All
: P3 Trivial with 2 votes (vote)
Target Milestone: ---
Assignee: Joost Andrae
QA Contact: issues@sw
URL:
Keywords:
: 7986 11728 18397 20533 21693 24268 27599 36379 40615 41579 50093 54483 (view as issue list)
Depends on:
Blocks:
 
Reported: 2002-04-30 13:42 UTC by gus3
Modified: 2013-08-07 14:41 UTC (History)
2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description gus3 2002-04-30 13:42:32 UTC 
If I have enabled auto-save, and the time comes for an automatic save, one or
two keystrokes may not be processed as input during the save. That is to say, I
may type "worthwhile", but what comes up is "wortwhile" or "worwhile".
Comment 1 prgmgr 2002-10-02 05:13:36 UTC 
*** Issue 7986 has been marked as a duplicate of this issue. ***
Comment 2 stefan.baltzer 2002-12-16 14:13:42 UTC 
In the worst case, the keyboard buffer should "spit out" the whole
string after the needed delay...
SBA->TM: This looks a little like the problem we talked about times
ago when the save-as dialog is called with shortcut and typing on too
fast cuts i.e. "D:\temp\blabla.sxw" to ":\temp\blabla.sxw".
Changed component to "Framework".
Reassigned to Thorsten.
Comment 3 thorsten.martens 2003-01-20 11:02:22 UTC 
TM->gus3: Please check this one with an OO 1.0.2. I wasn`t able to
reproduce this problem with that version.
Comment 4 gus3 2003-01-26 05:44:31 UTC 
Sorry, it's still doing it. I was able to get it to drop a keystroke
during 3 consecutive auto-saves.
Comment 5 thorsten.martens 2003-02-13 14:56:49 UTC 
TM->MBA: As talked about, please have a look. Thanks !
Comment 6 tamblyne 2003-08-19 15:53:24 UTC 
*** Issue 18397 has been marked as a duplicate of this issue. ***
Comment 7 Mathias_Bauer 2003-09-10 11:42:50 UTC 
.
Comment 8 Mathias_Bauer 2003-09-10 11:49:49 UTC 
.
Comment 9 mikhail.voytenko 2003-09-12 11:42:30 UTC 
.
Comment 10 jack.warchold 2003-09-22 14:16:38 UTC 
*** Issue 11728 has been marked as a duplicate of this issue. ***
Comment 11 lohmaier 2003-10-01 23:15:02 UTC 
*** Issue 20533 has been marked as a duplicate of this issue. ***
Comment 12 askoning 2004-01-10 13:56:22 UTC 
*** Issue 24268 has been marked as a duplicate of this issue. ***
Comment 13 lohmaier 2004-04-09 21:37:09 UTC 
*** Issue 27599 has been marked as a duplicate of this issue. ***
Comment 14 bobharvey 2004-04-10 09:56:03 UTC 
I made my report, 7986, in september 2002, 6 months after this was first raised.
 I notice that it is not due for resolution until version 2 - given the slowness
with which the version numbers are consumed, just how far away is that?  Year 2008?

I happen to think that a word processor that drops letters is quite badly
broken, particularly from a touch-typist's point of view (I do 30 to 35 words
per minute in full flow)

Now, don't get me wrong: I like the product and I am supportive - almost
addicted - to the FLOSS concept.  I admire everything that has been done.  But I
feel a sense of proportion is missing over this issue.
Comment 15 mikhail.voytenko 2004-04-23 16:47:03 UTC 
MAV->AS: If I am not wrong you are working on this problem. So I send the bug to
you.
Comment 16 andreas.schluens 2004-04-26 06:37:14 UTC 
.
Comment 17 andreas.schluens 2004-04-30 07:16:20 UTC 
I`ve implemented the new AutoSave feature. And it checks for an user idle period
to save the current active documents. So the user shouldnt loos its key input ...
A test will show the results.
Comment 18 andreas.schluens 2004-11-12 07:02:31 UTC 
Reopened for sending bug back to the QA
Comment 19 andreas.schluens 2004-11-12 07:04:10 UTC 
Reaasign issue to JA
Comment 20 andreas.schluens 2004-11-12 07:04:28 UTC 
Restore Fixed state
Comment 21 lohmaier 2004-11-16 17:38:19 UTC 
*** Issue 36379 has been marked as a duplicate of this issue. ***
Comment 22 ingenstans 2004-11-16 20:15:11 UTC 
when is it meant to be integrated? It is still present in m60, so either it is 
not fixed, or the fix has not been integrated.
Comment 23 fanen 2004-11-17 11:15:44 UTC 
the issue is still presentin v 1.9.56 so the "fixed" state is quite  confusing...
Comment 24 Joost Andrae 2004-11-17 12:08:06 UTC 
JA: verified within cws recovery04. 
JA->Others: it will need additional time to get this child workspace integrated
into the OOo 2.0 master build...please stay tuned...
Comment 25 Joost Andrae 2004-12-08 15:00:21 UTC 
JA: verified in m65 master build
Comment 26 lohmaier 2005-01-14 20:49:34 UTC 
*** Issue 40615 has been marked as a duplicate of this issue. ***
Comment 27 lohmaier 2005-01-15 17:30:39 UTC 
*** Issue 40615 has been marked as a duplicate of this issue. ***
Comment 28 lohmaier 2005-01-28 22:31:08 UTC 
*** Issue 41579 has been marked as a duplicate of this issue. ***
Comment 29 lohmaier 2005-05-31 10:48:13 UTC 
*** Issue 21693 has been marked as a duplicate of this issue. ***
Comment 30 lohmaier 2005-05-31 10:51:05 UTC 
*** Issue 50093 has been marked as a duplicate of this issue. ***
Comment 31 lohmaier 2005-09-12 21:14:35 UTC 
*** Issue 54483 has been marked as a duplicate of this issue. ***
Comment 32 bobharvey 2006-04-23 22:18:40 UTC 
http://www.openoffice.org/issues/show_bug.cgi?id=64530 makes interesting 
reading.
Comment 33 Rainer Bielefeld 2013-07-23 05:49:58 UTC 
Change OS to ALL due to DUPs

I wonder what the fix might have been