AFAIK, yes, this is typical of word processors, or at least Word.
If we change the behavior, except to make it configurable (works this
way or works more like a traditional editor), I think we should discuss
what could be a better behavior.
The problem starts from the idea that Word keeps track of two different
"cursors" -- the "insertion point" and the "mouse cursor". If you move
the mouse cursor under some circumstances, the insertion point does not
move. If, after moving the mouse cursor, you use PageUp or PageDown
(and certain other keystrokes) the movement is not from the current
location of the mouse cursor but from the current location of the
insertion point, which can be significantly different.
As I write this, I suspect there are cases where the word processor
behavior makes sense, but I have not tried to list them. Anybody else?
Randy Kramer
Jesper Skov wrote:
>
> >>>>> "Mike" == Mike Nordell <[EMAIL PROTECTED]> writes:
>
> Mike> In all Windows applications, PageUp/Down moves the cursor. In
> Mike> AbiWord this is apparently not so right now.
>
> Mike> Page Up/Down only displays another area of the document (where
> Mike> the cursor _should_ have been), but a simple CursorUp after
> Mike> moving quite a few pages in a document took me back to where AW
> Mike> believed my cursor should be. Pissed off? Me? :-) Yes.
>
> Mike> Please tell me this is no design decision, just an oversight.
>
> Mike> If this is a Macintosh induced design decision, I think, nay I
> Mike> know, we will need to put cursor movement in a platform or
> Mike> preference layer.
>
> This is standard word processor brain damage, AFAIK. I hate is as
> well. But we hate it because we're used to editors which behave
> differently.
>
> I believe we have a bug about making the behavior configurable.
>
> FWIW I think ctrl-pageup/down DTRT.
>
> Jesper
