|
|
Post by shunpiker on Nov 30, 2005 0:15:38 GMT
Sometimes when I go back to type something in the middle (i.e. not at the end) of a document, the cursor magically jumps to the end of the document. This will sometimes have the effect that one character is inserted at the point where I wanted to type, and then the rest of the characters are appended to the end of the document, where the cursor remains.
I have not been able to determine exactly what triggers this behavior, or exactly how to make it stop -- but if I fiddle around (use arrow keys, scroll up and down, cut and paste) -- eventually it lets me edit the part of the document that I want to edit.
I believe I have seen it happen in Binder, Compose and Draft modes. This happens both in and out of full screen mode.
|
|
|
|
Post by KB on Nov 30, 2005 9:47:42 GMT
I can't reproduce this, although I do have the feeling that this may have happened to me a while ago. If you could find exact steps to reproduce it, that would be helpful. It may have something to do with the current selection state-saving, though, which is buggy anyway and will change within the next couple of beta versions. If you can find the steps to reproduce, though, I would be grateful.
Thanks,
Keith
|
|
|
|
Post by shunpiker on Nov 30, 2005 22:49:33 GMT
I have repro!
The trick is to save the document -- either Save or Save All, and use either the File menu or the keyboard shortcuts. Immediately after saving, the first keystroke will go to the insertion point, but then the cursor jumps to the end of the document where successive keystrokes will be applied.
|
|
|
|
Post by KB on Nov 30, 2005 23:20:19 GMT
Thanks. Hmm. I can reproduce this only in Draft view. In Binder and all other views it works fine for me, but in Draft view I see exactly the problem you are describing. Does that sound right to you or do you see it elsewhere too? I will certainly look into fixing the Draft problem...
Thanks again,
Keith
UPDATE: Okay, I've found what's causing it - it's a silly one. Will fix it for the next beta (so far it only looks like it affects Draft mode, but I will look at the other modes too just to be sure).
|
|
|
|
Post by shunpiker on Nov 30, 2005 23:55:04 GMT
Thanks!
I may have over-reported the bug. I can only reproduce it in draft mode, and even then, not in full-screen mode.
I thought I saw it in the other modes and in full screen, because switching modes is one of the ways which I tried to get around this problem. Perhaps that worked and I didn't notice it.
In any case, I'll let you know if I see the problem happen in any other mode.
|
|
amberv
Junior Member
Posts: 99
|
Post by amberv on Dec 1, 2005 3:39:33 GMT
Addenda: Looks like I should read the whole thread before I wax eloquent. :)
I can reproduce this. As soon as you switch to Draft view, if you click into the text area and begin typing, the first character will be placed at the cursor, and then the cursor will jump to the end of the section you are in. If you continue typing, everything will appear at the end until you once again click anywhere in the current section. Cursor operation will then be normal until...
You either click on a new section in the Draft browser, or click in a new section in the text area. Then the same bug will show up, and be resolved with the above method. This is reproducible 100% of the time for me. The only trick is, once you have "broken in" a section, going back to it does not cause the bug. Switching back out of Draft and back in will not cause the bug in the broken in sections.
Hence, the bug is tied to creating an un-saved version, in Draft, when you first begin typing. Once an un-saved version exists -- the bug does not appear.
And the previous poster is right, this does not seem to happen in Full Screen for whatever reason.
|
|
