The Play/Pause button and the Loop checkbox now have images. Parameter names beside sliding controls are now displayed using 2-D Math.

$$\begin{gathered} \mathrm{Explore}\left( \mathrm{plot}\left(\mathrm{alpha}\cdot \sin \left(x\right)\,x\= -2\cdot \mathrm{Pi} .. 2\cdot \mathrm{Pi}\, \mathrm{view}\=-1..1\right)\, \\ \mathrm{parameters}\=\left[ \mathrm{alpha}\=-1.0 .. 1.0 \right]\, \\ \mathrm{placement}\=\mathrm{left}\, \mathrm{animate}\, \mathrm{loop}\, \mathrm{size}\=\left[300\,300\right] \right) \end{gathered}$$

The orientation of Slider controls is now respected and can be specified similarly to other control characteristics. A separate orientation option can be used for all Slider controls, which can be overridden in each parameter's individual specification. The orientation also affects the layout of the control's name, current value label, and animation checkbox.

$$\begin{gathered} \mathrm{Explore}\left( \mathrm{plot}\left(\mathrm{magnitude}\*\sin \left(\mathrm{scale}\*x\+\mathrm{shift}\right)\,x\=-2\*\mathrm{Pi}..2\*\mathrm{Pi}\,\mathrm{view}\=-1..1\right)\, \\ \mathrm{parameters}\=\left[ \mathrm{scale}\=1.0..5\, \\ \left[\mathrm{shift}\=-\mathrm{Pi}..\mathrm{Pi}\, \mathrm{placement}\=\mathrm{bottom}\, \mathrm{orientation}\=\mathrm{horizontal}\right]\, \\ \left[\mathrm{magnitude}\=-1..1.0\, \mathrm{placement}\=\mathrm{right} \right] \right]\, \\ \mathrm{placement}\=\mathrm{left}\, \mathrm{orientation}\=\mathrm{vertical}\, \mathrm{size}\=\left[300\,300\right] \right)\; \end{gathered}$$

When several controls are placed together, they are grouped according to orientation. For example, when placement is to the left of the plotting component then vertically oriented Sliders are stacked horizontally and appear above horizontally oriented Sliders which are stacked vertically.

$$\begin{gathered} \mathrm{Explore}\left( \mathrm{plot}\left(\mathrm{magnitude}\*\sin \left(\mathrm{scale}\*x\+\frac{\mathrm{shift}\cdot \mathrm{Pi}}{2}\right)\,x\=-2\*\mathrm{Pi}..2\*\mathrm{Pi}\,\mathrm{view}\=-1..1\right)\, \\ \mathrm{parameters}\=\left[ \mathrm{scale}\=1.0..5\, \\ \left[\mathrm{shift}\= 0.. 4\, \mathrm{orientation}\=\mathrm{horizontal}\right]\, \\ \mathrm{magnitude}\=-1..1.0 \right]\, \\ \mathrm{placement}\=\mathrm{left}\, \mathrm{orientation}\=\mathrm{vertical} \right)\; \end{gathered}$$

You can now customize the appearance of markers in a 2-D plot exploration as well as fix one of the coordinates of a marker.

To customize the appearance of a marker, use the plot options color, symbol, and symbolsize in the markers options sequence. By default, all markers have the same customizations, but you can override the default customization by setting customizations for individual markers. For example, in the following Explore command call, all of the markers have their appearance set to color=blue, symbol=solidcircle, and symbolsize=25, except for the first and $n$th markers (where the color=red option overrides the color=blue option).

To fix one of the coordinates of a marker, specify a fixed numeric value for that coordinate. In the following example, all of the markers have fixed horizontal positions (specified by the list xini). Their vertical positions, however, are set to variable parameters. In the exploration, you can change the vertical position of any of the markers but you cannot change their horizontal positions.

Note: To try this or any other example on this page, select View > Open Page as Worksheet, and then execute the commands.

$$\begin{gathered} F ≔ \mathbf{proc}\left(\mathrm{data}\colon\colon \mathrm{list}\, n\colon\colon \mathrm{posint}\right) \\ \mathbf{local} S\,x\; \\ S ≔ \mathrm{CurveFitting}:-\mathrm{Spline}\left(\mathrm{data}\,x\,\mathrm{degree}\=n\right)\; \\ \mathrm{plots}:-\mathrm{display}\left( \mathrm{plot}\left( S\, x \= -1.0 .. 0.0\, \mathrm{color}\=\mathrm{red} \right)\, \\ \mathrm{plot}\left( S\, x \= 0.0 .. 3.5\, \mathrm{color}\=\mathrm{blue} \right)\, \\ \mathrm{plot}\left( S\, x \= 3.5 .. 4.5\, \mathrm{color}\=\mathrm{red} \right)\, \\ \mathrm{view}\=-2..5\right)\; \\ \mathbf{end} \mathbf{proc}\: \\ \mathrm{xini}\,\mathrm{yini} ≔ \left[0.0\,0.5\,1.1\,1.7\,2.4\,3.5\right]\, \left[2.0\,1.5\,0.1\, -0.5\,2.6\,2.2\right]\: \\ N ≔ \mathrm{numelems}\left(\mathrm{xini}\right)\: \\ \mathrm{prng} ≔ -1.0..4.0\: \\ \mathrm{Explore}\left( F\left(\left[\left[0\,\mathrm{y1}\right]\,\left[0.5\,\mathrm{y2}\right]\,\left[1.1\,\mathrm{y3}\right]\,\left[1.7\,\mathrm{y4}\right]\,\left[2.4\,\mathrm{y5}\right]\,\left[3.5\,\mathrm{y6}\right]\right]\, n\right)\, \\ \mathrm{parameters} \= \left[ \left[n\=1..7\, \mathrm{label}\=\mathrm{degree}\right]\, \\ \mathrm{seq}\left( y\parallel i\=\mathrm{prng}\, i\=1..N \right) \right]\, \\ \mathbf{markers} \= \left[ \left[ \mathrm{xini}\left[1\right]\,\mathrm{y1}\,\mathbf{color}\mathbf{\=}\mathbf{red}\mathbf{ }\right]\, \\ \mathrm{seq}\left( \left[\mathrm{xini}\left[i\right]\,\mathrm{y}\parallel \mathrm{i} \right]\, \mathrm{i}\=2.. \mathrm{N}-1 \right)\, \\ \left[ \mathrm{xini}\left[N\right]\,\mathrm{y}\parallel \mathrm{N}\,\mathbf{color}\mathbf{\=}\mathbf{red}\mathbf{ }\right] \, \mathit{color}\mathbf{\=}\mathit{blue}\mathbf{\,}\mathbf{ }\mathit{symbol}\mathbf{\=}\mathit{solidcircle}\mathbf{\,}\mathbf{ }\mathbf{ }\mathit{symbolsize}\mathbf{\=}\mathbf{25}\right]\, \\ \mathrm{initialvalues} \= \left[ \mathrm{seq}\left( y\parallel i\=\mathrm{yini}\left[i\right]\, i\=1.. N \right)\, n\=5 \right]\, \\ \mathrm{title}\=''Spline\; Interpolation'' \right) \: \end{gathered}$$

A parameter which takes on values of true and false can now have its controller be a CheckBox. This is the default for a parameter whose values are specified by a two-element list containing entries true and false.

In the following example, the parameter tf with label gridlines is controlled by a CheckBox component. Notice that you can select and clear gridlines while the exploration's animation is running.

$$\begin{gathered} \mathrm{Explore}\left( \mathrm{plot}\left(\sin \left(a\*x\right)\,x\=-\mathrm{Pi}..\mathrm{Pi}\,\mathrm{view}\=-1..1\, \mathrm{gridlines}\=\mathrm{tf}\right)\, \\ \mathrm{parameters}\=\left[ \left[\mathbf{ }\mathit{tf}\mathbf{\=}\left[\mathit{true}\mathbf{\,}\mathit{false}\right]\mathbf{\,}\mathbf{ }\mathit{label}\mathbf{\=}\mathit{gridlines}\mathbf{ }\right]\, \\ a\=1.0..10\right]\, \\ \mathrm{placement}\=\mathrm{left}\, \mathrm{size}\=\left[400\,300\right]\, \mathrm{loop}\, \mathrm{numframes}\=20 \right) \end{gathered}$$

Although the same example can be constructed by setting controller=combobox for parameter tf, you cannot change the value of gridlines while the animation is playing as you can with CheckBox component.

$$\begin{gathered} \mathrm{Explore}\left( \mathrm{plot}\left(\cos \left(a\*x\right)\,x\=-\mathrm{Pi}..\mathrm{Pi}\,\mathrm{view}\=-1..1\, \mathrm{gridlines}\=\mathrm{tf}\right)\, \\ \mathrm{parameters}\=\left[ \left[\mathbf{ }\mathit{tf}\mathbf{\=}\left[\mathit{true}\mathbf{\,}\mathit{false}\right]\mathbf{\,}\mathbf{ }\mathit{label}\mathbf{\=}\mathit{gridlines}\mathbf{\,}\mathbf{ }\mathit{controller}\mathbf{\=}\mathit{combobox}\mathbf{ }\right]\, \\ a\=1.0..10\right]\, \\ \mathrm{placement}\=\mathrm{left}\, \mathrm{size}\=\left[400\,300\right]\, \mathrm{loop}\, \mathrm{numframes}\=20 \right) \end{gathered}$$

Finally, it is not necessary to give a list of values when you specify the controller as checkbox.

$$\begin{gathered} \mathrm{Explore}\left( \mathrm{plot}\left(\tan \left(a\*x\right)\,x\=-\mathrm{Pi}..\mathrm{Pi}\,\mathrm{view}\=-8..8\, \mathrm{gridlines}\=\mathrm{tf}\right)\, \\ \mathrm{parameters}\=\left[ \left[\mathbf{ }\mathit{tf}\mathbf{\,}\mathbf{ }\mathit{label}\mathbf{\=}\mathit{gridlines}\mathbf{\,}\mathbf{ }\mathit{controller}\mathbf{\=}\mathit{checkbox}\mathbf{ }\right]\, \\ a\=1.0..10\right]\, \\ \mathrm{placement}\=\mathrm{left}\, \mathrm{size}\=\left[400\,300\right]\, \mathrm{loop}\, \mathrm{numframes}\=20 \right) \end{gathered}$$

The newsheet option for Explore opens your exploration in a new Document instead of the current document. This is convenient for creating applications or assignments. However, in previous versions of Maple, if your exploration depended on names not defined in Maple (for example, a procedure or a module that you wrote), you needed to copy the code for these names into the new Document and then execute the code before running the exploration. This process has been simplified with the new startupdefinitions option.

The startupdefinitions option inserts assignment statements into the Startup Code region of the new Document. When the new Document opens, these assignment statements are executed automatically and your exploration is ready to run. The following sections give two examples to illustrate how this works. The first example shows how to insert a procedure into the Startup Code region of a new Document. The second example shows how to insert an unevaluated module into the Startup Code region.

Inserting a procedure

In the following example, the Cobweb procedure produces a cobweb plot for the logistic map, r$x$(1-x). The newsheet option causes the exploration to start in a new Document. The startupdefinitions option inserts the code that assigns the Cobweb procedure to the Cobweb name into the Startup Code region of the new Document. This allows the exploration to function directly after opening. $$\begin{gathered} \mathrm{Cobweb} ≔ \mathbf{proc}\left( r\, \mathrm{x0}\, \left\{\mathrm{numpoints}\colon\colon \mathrm{posint}≔1\right\} \right) \\ \mathbf{local} f\,i\,M\,N\,x\; \\ N≔2\cdot \mathrm{numpoints}\; \\ f≔\left(x\,r\right)\to r\cdot x\cdot \left(1-x\right)\; \\ M≔\mathrm{Matrix}\left(N\,2\,\mathrm{datatype}\=\mathrm{float}\left[8\right]\right)\; \\ M\left[1\,1\right]\,M\left[1\,2\right]≔\mathrm{x0}\,0\; \\ M\left[2\,1\right]\,M\left[2\,2\right]≔M\left[1\,1\right]\,f\left(M\left[1\,1\right]\,r\right)\; \\ \mathbf{for} i \mathbf{from} 3 \mathbf{to} N-1 \mathbf{by} 2 \mathbf{do} \\ M\left[i\,1\right]\,M\left[i\,2\right]≔M\left[i-1\,1\right]\,f\left(M\left[i-1\,1\right]\,r\right)\; \\ M\left[i\+1\,1\right]\, \end{gathered}$$