Things Desmos Can't Do (Yet)
There are a lot of things that seem like they should be possible in Desmos, but aren't. These are listed below, along with explanations as to why they don't work and (in some cases) partial fixes.
Generalized iteration #
Desmos does not support generalized iteration without actions. List comprehensions and recursion can be used to achieve almost complete iteration without actions.
Lists of Lists (Nested Lists) #
Desmos does not support lists of lists, lists of lists of lists, or any other nesting of lists directly. However, there are a few partial workarounds for this:
Polygon .vertices #
Polygons in the geometry calculator have a property which can be used to access their points. Because polygons can themselves be put into lists, this feature can be used to access a list of points inside of a list of polygons. In other words, you have a list of lists of points.
Higher-dimensional indexing #
If your inner lists are all the same length, lists can be indexed in a multi-dimensional manner. For instance, for a list representing a 10 by 10 grid, you could use a 100-element list to store all the elements. Here is a function that, given such a list , gets an item at a 2D position: . Note that we are trying to preserve Desmos's "indices start at 1" convention here.
Lists greater than 10000 elements long #
This does not work. However, there are many workarounds that allow for >10000-element lists. Do keep in mind that all of these have their own caveats.
Matrices #
Desmos does not support matrices outside of its (somewhat limited) Matrix Calculator. However, you can emulate them with lists and implement the matrix operations yourself.
Current Viewport/Graphpaper Bounds Variables #
Desmos does not have a way of telling your graph where on the graphpaper the user has currently focused. The developers have cited flickering-related bugs as the main reason why they have not implemented this feature yet. The closest thing that exists are the and variables, which get the size of the viewport in pixels. In practice, they're most useful for finding the aspect ratio (ratio of width to height) of the viewport and adjusting onscreen elements to work better on larger and smaller screens.
Desmos does however let you control the viewport with variables, but this will also prvent the user from moving it themselves. Note that in the 3d calculator this only lets you control the graph bounds and not the actual camera position or orientation.
Orientation Variables (3D Calculator) #
In the 3D calculator, Desmos does not have variables for determining the current camera orientation. As such, you cannot make graphs that change shape based on the direction in which the user is facing.