Closed stefnotch closed 2 years ago
Typing tan doesn't work. However, typing a*tan works
This is probably a result of the first character inputted is not being parsed into the function recognizer. For example:
tan
does not recognize the expression
f [Backspace] tan
recognizes tan
sin
results in s ∈
as in s "in"
s [Backspace] sin
results in sin
Adding shortcuts[':'] = '\\coloneq'
to ExpressionElement.vue
would be useful
shortcuts[':'] = {
mode: 'math',
value: '\\coloneq',
}
Typing tan doesn't work. However, typing a*tan works
This is probably a result of the first character inputted is not being parsed into the function recognizer. For example:
tan
does not recognize the expressionf [Backspace] tan
recognizestan
sin
results ins ∈
as ins "in"
s [Backspace] sin
results insin
Your guess is spot on. I investigated this a bit more and apparently, mathlive only calls that in
to ∈
logic when receiving keyboard events. (Mathlive has an internal keystroke buffer. It is a somewhat hack-ish way of keeping track of the last few characters, checking if they match something and then replacing it with the something)
Another random issue
If you try to assign a value to
pi
, and press enter, the cursor will keep on blinking, even if you edit another thing (so you can have multiple cursor blinking at the same time).
Basically, type a[Backspace]pi:3
Hmm, for some reason I am no seeing this in my instance
Okay, odd, I'm also struggling to reproduce this. I suppose it's worth keeping out an eye for.
Another piece of feedback I got
a small nit in Quantumsheets: the input boxes capture my scroll events, so if my mouse is somewhere in the doc and I scroll down and intersect one, it stops
Typing tan doesn't work. However, typing a*tan works
This is probably a result of the first character inputted is not being parsed into the function recognizer. For example:
tan
does not recognize the expressionf [Backspace] tan
recognizestan
sin
results ins ∈
as ins "in"
s [Backspace] sin
results insin
Your guess is spot on. I investigated this a bit more and apparently, mathlive only calls that
in
to∈
logic when receiving keyboard events. (Mathlive has an internal keystroke buffer. It is a somewhat hack-ish way of keeping track of the last few characters, checking if they match something and then replacing it with the something)
I pushed a little hack/workaround for this 71e1cbdb096da4a56c158392917f88d325967d8e We should eventually find a proper fix/report this on the mathlive repository/submit a pull request for a "insert a letter as if the user typed it" function over there
Another piece of feedback I got
a small nit in Quantumsheets: the input boxes capture my scroll events, so if my mouse is somewhere in the doc and I scroll down and intersect one, it stops
That issue has been reported at https://github.com/arnog/mathlive/issues/1146 For now I'm locally fixing mathlive before deploying it.
Alright, I also fixed the feedback about the escape to exit the mathfield.
Let's close this issue, since this issue is pretty much all fixed. If we encounter more such little quality of life issues, we can open new ones
It switches between the normal mode and the command mode. Replace that with a
Esc
to escape command mode andEsc
to escape the mathfield.Completed!
> This might be a bit annoying. > ![hq13L7GHFl](https://user-images.githubusercontent.com/10220080/92574538-7ffcc480-f287-11ea-9d58-62a550d5e3d9.gif) > When you want to make the `:=` and type `[:] -> [something else] -> [Backspace] -> [=]`, it doesn't make it. Yep, that's annoying. I'll have to fix that. > If you don't need the colon for anything else, you could make it like MathCAD does, so you only need to type `:`. Good idea. That would also make typing `:=[Backspace]` less annoying.Yeah, true
Uhhh, seems like it.