So does this mean simpleFunction( is no longer needed to convert, for example, a string that student types into a math input into something that for a graph component can display?
A latex string is different than the output of simpleFunction (a function object). Latex strings can be functions, but they could also be arbitrary expressions… x + y + z < 3.
So you still need to use simpleFunction(latex) to try and interpret the latex as a function.
Sorry, but I’m lost here on what this change really means, or how to use it. I am sure it is very cool but I am not sure how I can learn more about it. Suggestions?
I keep making this same request (to expand the LaTeX characters available) every couple of months. I feel embarrassed trying to write limits and matrix expressions that are native to Mathquill (Desmos’s typesetting engine) but that Desmos has deliberately disabled (because the calculator doesn’t evaluate those limits).
I didn’t realise matrices were an option in Mathquill. I have been using \binom and spaces to make 2x1 and 2x2 matrices but they look pretty amateurish.
Just to clear up some issues here about Mathquill and Desmos:
Desmos has a Matrix calculator so there would seem to be no particular reason it can’t render them in Activities, except that they’re disabled.
Limits though are a different story.
Mathquill does support Limits(and so does Desmos) but they’re rendered in what is known as \textstyle format rather than \displaystyle format, which basically means adjacent subscript style rather than underscript style(which is what we all want).
There is an unresolved issue on the Mathquill Github page about this exact behaviour, so until that is addressed, it’s not likely Desmos can do anything.
I can’t get limits to display in textstyle. No variant of \lim, \\lim, \mathoperator{lim} etc. will display a limit. Desmos just reads it as “lim” instead of “\lim”.
I’d love to hear that I’m wrong and you know of a way to get limits to display as math.
Not a dumb question at all. You’d like - we’d all like - for the usual latex syntax to work in Desmos but it often doesn’t. In my experience the best option is almost always to use html entities for representation.
In this case, for a right arrow, you really want to use: → which even here in the forum encodes directly to: →
All this stuff is kinda hacky. There really should be a more Latex-consistent way of doing this. I’m just lucky that I really love front end development and am familiar with some of these other ways of rendering things on the web. So not a dumb question at all.
Is there somewhere to find a reference chart of how to type things in properly? I think that would be very helpful for the less experienced like me! (Limits, over bars, angles, matrices, summation, etc.)b
I am SO EXCITED about the new features we are seeing! I would also LOVE to see better Latex function for limits. I am not well-versed on these terms, Mathquill and \textstyle and what all of that means, but I figured out just enough Latex to get limits to display how I want in other environments, but I SO DISLIKE the way it can be done on Desmos that I have literally resorted to using images instead for every.single.limit.expression… super tedious!! But I am much happier with how it looks. Would LOVE to see a fix for this!
Can anyone answer Carla’s question? I would like to see the same thing. I am very new to CL and would like to learn more but don’t even know where to start.
But for getting familiar with other ways of writing stuff - and especially for things Desmos cares not to support in their graphs at the moment - there are many great sources out there. You’ll find lots of things just by googling, but Overleaf tends to be a good resource, such as for example this page.
Just be aware that there are many different Latex packages and versions out there that may or may not be compatible with Mathquill or what Desmos supports.
I get a lot of good beginner latex from the EquatIO app for Chrome. They have one for windows, but the Chrome version can add equations directly to Google Docs. Also, Debbie in this chain of emails has a good source.