I found out that there is actually a bug involving the display of points. If you give a point an opacity OR point size of normaldist( ), the desmos graph freezes up! A very unique crash, I’ve never seen this before. And I found this error hunting (as usual)
Another note is that this works in every calculator (3d, graphing, geometry).
ANOTHER UPDATE: This actually isn’t restricted to points. Any “shape” that requires you to give size/thickness and/or opacity will break if you give it normaldist()
A follow up is that you can actually fix this by first providing a valid opacity (It won’t fix right now because the graph is in some kind of freeze-state), and then deleting every single expression. Then, press the undo button which apparently refreshes the graph and fixes everything!
This won’t work with the example because for some reason you can’t edit the point.
If you zoom into a line / function, cause this bug, and zoom out, the function line wont “zoom back out”, its just stuck at where the camera was original at
You can’t plot any lines or anything. (The graph is frozen)
If you play a slider, make a “display” of it, then cause the error, the display of it will freeze. 1. Here
Can you recreate this, but use a variable instead of directly using normalDist() in the point’s parameters? It would make it easier to check out because you can actually see the opacity definition, or change the variable definition to regain access to the parameters without building a new graph from scratch.
Also, normaldist() outputs a curve, so you don’t get discrete values to use for the opacity. To have dynamic opacity, you need a value (or a list), although it is interesting that other invalid inputs still allow you to access the parameters.
Also note that changing the variable doesn’t change the crash-state of the graph. As soon as you give the point normaldist() and the parser evaluates it, it will crash.
Me and my friend assume that since it is a function extending infinitely, Desmos can’t evaluate it properly and due to its poor rendering pipeline all other expressions are not evaluated, and other “updates” aren’t either.
Also I wanted to add on, they successfully caught expressions like x = 1 (which also extend infinitely) and prevented the crash, but they just forgot about the distribution functions (normaldist, poissondist, uniformdist,binomialdist,chisqdist,tdist, which all can work just like normaldist)
