On Wed, 27 Jan 2010 14:37:33 -0600
"Edward K. Ream" <[email protected]> wrote:
> We are pretty much done, and pretty much stuck. There is, imo, a real
> and severe bug with cursor.movePosition.
I'm not convinced. Given the characters:
a K b M c N d
where a-d are cursor placements and K, M, and N are unicode characters, and K
is one of the unicode-combining characters, qt will report positions n, n+2,
n+3, and n+4 for a,b,c, and d.
But when you move through it with the cursor keys it only takes three key
strokes, a->b, b->c, and c->d. So if cursor.movePosition is supposed to behave
like the user pressing the keys, it's making sense.
I don't think qt's being inconsistent, just incompatible with the code that
evolved against a tk model.
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.
