N
Nicolas Rabaté
Hello,
I'm using the word application event model, more especially WindowSelectionChange.
In the particular situation I will describe, Sel.Start, Sel.End and
Sel.StoryLength are offseted by 127. The bug is consistent across Word 2K or
Word XP, no matter the SP's are. I haven't checked 2K3 yet.
Say the user type 5 characters in a new document. Select some of the
characters.
Do a cut. A WindowSelectionChange is trigerred. When the
WindowSelectionChange is entered Sel.Start and Sel.End are audited thanks to
debug.print or the watch. Nothing wrong at this stage. They are set to expected values.
Now, instead or doing a cut, type any character, a space for instance. When
the WindowSelectionChange is entered Sel.Start, Sel.End, StoryLength are
wrong. They are offseted by 127.
Is it a known bug?
Is there a workaround?
Thank you
I'm using the word application event model, more especially WindowSelectionChange.
In the particular situation I will describe, Sel.Start, Sel.End and
Sel.StoryLength are offseted by 127. The bug is consistent across Word 2K or
Word XP, no matter the SP's are. I haven't checked 2K3 yet.
Say the user type 5 characters in a new document. Select some of the
characters.
Do a cut. A WindowSelectionChange is trigerred. When the
WindowSelectionChange is entered Sel.Start and Sel.End are audited thanks to
debug.print or the watch. Nothing wrong at this stage. They are set to expected values.
Now, instead or doing a cut, type any character, a space for instance. When
the WindowSelectionChange is entered Sel.Start, Sel.End, StoryLength are
wrong. They are offseted by 127.
Is it a known bug?
Is there a workaround?
Thank you