Desmos API v1.1 released
desmos-api-announce
Desmos is very happy to announce the release of version 1.1 of the Desmos API.
This release is part of our scheduled release cycle, and we recommend all users upgrade to this version. Benefits of upgrading include:
remaining consistent with what students see on high-stakes tests in states where Desmos is embedded in the test platform.
offering an experience for students in your product similar to the one at desmos.com.
ensuring the best interaction with the latest browsers and platforms.
We will help all of our partners upgrade to version 1.1 in a timely fashion. Please email Chris Lusto (ch...@desmos.com) or Jason Merrill (ja...@desmos.com) with any questions.
New Features:
In version 1.1 we are introducing new features to give you more flexibility and consistency in setting display styles, access to more information about the status of each expression, and better accessibility options in the basic calculators.
Use more drawing styles in more places. Even though they can often be used interchangeably in graphs, tables and point lists previously supported very different sets of display options. Now they both allow for a single, unified set of display options containing the best of both worlds. It’s also possible to set the fill and fillOpacity properties of parametric curves and polygons.
Get more information about the current status of expressions. The GraphingCalculator.expressionAnalysis observable object now contains more useful information, including an expression’s evaluated numeric value (or list of numeric values) and whether or not Desmos displays that evaluation in the expressions list.
Take advantage of better accessibility options. The basic calculators support Braille input and output, including refreshable Braille displays, out of the box. The Braille mode can be set to either UEB or Nemeth through the settings menu or via constructor options. For those who want to enter six-dot Braille characters without a specialized device, the sixKeyInput option lets users do that using the home row on a standard keyboard. The basic calculators now also support projectorMode.
Use uniaxial scaling without a touch device. On devices that support multi-touch, it is possible to scale a single axis using a pinch-zoom gesture along an axis. That same functionality has been extended to non-touch devices by holding the SHIFT key and dragging or scrolling along one of the axes.
Enforce degreeMode more consistently. Because degreeMode is both constructor option and a property of graph states, resetting a graph to a blank state (either through the UI or a call to GraphingCalculator.setBlank()) will leave the graph in radian mode, regardless of the degreeMode constructor option. There is now an option called clearIntoDegreeMode that will preserve degreeMode even after the graph has been cleared.
Code Update:
Because a single expression can now contain both points and line segments that may be styled separately, a single style property is no longer sufficient to describe all of the possible display options, so it has been deprecated. When specifying display styles through GraphingCalculator.setExpression(), you should set pointStyle and lineStyle properties separately. The style property will continue be supported in v1.1, but it will log a warning to the console and may be removed in future versions.
Similarly, the columnMode property for table columns has been deprecated in favor of the separate boolean properties called points and lines that control point and line visibility, respectively. Setting a columnMode through GraphingCalculator.setExpression() will continue to work in v1.1 but it will log a warning to the console and may be removed in future versions.
lockViewport and zoomButtons are considered to be incompatible. Setting both options to true will log a warning to the console and override the zoomButtons option by setting it to false.