verybadcat/CSharpMath

Editor cursor should match the size of surrounding display

Happypig375 opened this issue · 5 comments

Describe the bug

  • Cursor is too small outside scripts
    image

  • Cursor is too large inside scripts in scripts
    image

Expected behavior

Editor cursor should match the size of surrounding display.

Environment (please complete the following information):

  • Platform: CSharpMath.Rendering
  • Package Version or Commit: 0.4.2
  • Device: UWP

Additional context

@charlesroddie This should be what you mean, right?

@charlesroddie This should be what you mean, right?

I think you got this feedback not from me but from Sophie and we need to interpret it. The original issue is "cursor too small on phones".

On Word the cursor is thin and tall, and doesn't vary with internal sizing of elements.

image
image

In LyX the cursor is thin and tall, and varies in a slightly complex way that corresponds to their substructures. (We shouldn't do this.)

image
image

Mathquill is thin and moderately tall, and does vary with internal sizing I think. (Subtle because their superscripts are not much smaller.)

image
image

I think:

  • We should go with the consensus of a thin cursor, which is "full height" for normal-sized text (not in subscripts).
  • This could be reduced in subscripts as in MathQuill and it would probably be an improvement but a very minor one.

Should the height be equal surrounding display or should there be extra height above and below?

Maybe more height above and below, either the same (LyX) or a bit more height above (Word).

If the cursor would become part of the LaTeX that is displayed (inserting "|" or something like that into the MathList just before displaying it), then it would match its surroundings automatically I think? Assuming that this symbol causes other symbols to move horizontally: when it is invisible temporarily because of cursor blinking, a transparent symbol of equal size should be used, so that the math does not "jump".

Unless we implement drawing or image TeX commands (which we won't), I don't think this can be achieved just with LaTeX.