On Tue, 2 Feb 2010 10:09:14 -0800 (PST) "Edward K. Ream" <[email protected]> wrote:
> Let me try to get this straight. Only 3 cursor movements are necessary > to step across all three characters, but when we are done we are at > position n+4. Right? How can this possibly be *not* a bug? If this is > in any sense correct, how is the cursor position useful? One of the characters is a unicode combining character, i.e. not meaningful by itself, but only as a modifier for the preceding character. Visually it's an extra wiggly bit drawn on the character it modifies. So there are four unicode characters but two of them are fused, using the keyboard you can't place the cursor between, except by placing it after them and, with no selection, hitting backspace, which deletes the modifier character, leaving the consonant part in it's simple form (at which point you're down to three characters). The movePosition function is mimicking what you can do with the keyboard. I don't know how this relates to the problem recreating the selection for the undo commands, unless you're using movePosition to create the selection, which I don't think will work for the above reasons. It seems the non-movePosition approach to create a selection would be setPosition(i, MoveMode=MoveAnchor); setPosition(j, MoveMode=KeepAnchor) But maybe that's not the problem - I'm not familiar with the undo code and who's creating the errant selection. I'd try and find a simple demo of the bugged behavior for reporting. Cheers -Terry -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
