Open ftolsson opened 2 years ago
This is the inferred behavior of NSTextView
. It moves around by DRAWN glyphs. Because these glyphs are drawn only when the cursor is on the actual line, text view has hard time understanding which index is which.
I'll have to study if I can somehow circumvent this.
Get it. But does it really need to check what's on the next line to correctly end up after the last glyph on this, though? I'm thinking that the the "after last glyph, but before CR" logic should look the same regardless?
A small quirk with hidden Fountain markup:
With hide markup OFF, and the caret at the beginning of the character name in this text:
and you hit END (or cmd + right arrow) the caret, as expected, goes to the right of the word character:
CHARACTER |
But if you turn it ON, hitting END will send the caret to the next line and past the hidden underscore, like this:
This is also true for asterisks. I'm guessing Beat should rather check where this line ends, but now probably checks where next begins?