In this design the user controls now contain no logic: they just pass mouse events to/from the back-end module. #637

Render() is called automatically when the number of plottables changes. This means that static plots typically do not require the user to call the render method. This option is configurable.

Configuration has moved from formsPlot1.Configure() to formsPlot1.Configuration which has documented fields. Although it's exposed in the control, it really lives in the backend module.

The demo applications are showing their age. They could probably benefit from a redesign. The most useful things to demonstrate would simple be:

• How to enable/disable panning and zooming
• How to lock an axis (e.g., you can pan horizontally but not vertically)
• How to link axes across multiple plots
• How to display live updating data (changing values in an array vs. growing data)
• How to implement custom right-click action