Added examples of .opts.clear() and .opts.show()
"cell_type": "markdown",
"metadata": {},
"source": [
- "The code is then a bit shorter and more readable with the same result, but it no longer tab completes, and so omitting the builder is probably only useful for a final, published set of code, not during exploration. When using the `.opts` method on compositions of elements (i.e., layouts or overlays) you still need to use the options builders to indicate which type of object the options should be applied to. For more information on options builders and how to use them appropriately, see the the [User Guide](../user_guide/03-Customizing_Plots.ipynb)."
+ "The code is then a bit shorter and more readable with the same result, but it no longer tab completes, and so omitting the builder is probably only useful for a final, published set of code, not during exploration. When using the `.opts` method on compositions of elements (i.e., layouts or overlays) you still need to use the options builders to indicate which type of object the options should be applied to. \n",
+ "\n",
+ "If you want to find out which options have been changed on a given object, you can use `.opts.show()`:"
+ ]
+ },
+ {
+ "cell_type": "code",
+ "execution_count": null,
+ "metadata": {},
+ "outputs": [],
+ "source": [
+ "dashed.opts.show()"
+ ]
+ },
+ {
+ "cell_type": "markdown",
+ "metadata": {},
+ "source": [
+ "For more information on how to work with options, see the the [User Guide](../user_guide/03-Customizing_Plots.ipynb)."
]
},
{
"cell_type": "markdown",
"metadata": {},
"source": [
- "Note how HoloViews remembered the Bokeh-specific styles we previously applied to the `spikes` object! This feature allows us to style objects once and then keep that styling as we work, without having to repeat the styles every time we work with that object. Note that even though this styling is associated with the element, it is not actually stored on it, which is mostly an implementation detail but does define a strict separation between what HoloViews considers parts of your data (the Element) and what is part of the \"look\" or the \"view\" of that data (the options associated with the object, but stored separately). You can learn more about the output utility and the options system in the [User Guide](../user_guide/03-Customizing_Plots.ipynb)."
+ "Note how HoloViews remembered the Bokeh-specific styles we previously applied to the `spikes` object! This feature allows us to style objects once and then keep that styling as we work, without having to repeat the styles every time we work with that object. Note that even though this styling is associated with the element, it is not actually stored on it, which is mostly an implementation detail but does define a strict separation between what HoloViews considers parts of your data (the Element) and what is part of the \"look\" or the \"view\" of that data (the options associated with the object, but stored separately). \n",
+ "\n",
+ "If we want to reset back to the original syling, we can call `.opts.clear()`:"
+ ]
+ },
+ {
+ "cell_type": "code",
+ "execution_count": null,
+ "metadata": {},
+ "outputs": [],
+ "source": [
+ "spikes.select(milliseconds=(2000,4000)).opts.clear()"
+ ]
+ },
+ {
+ "cell_type": "markdown",
+ "metadata": {},
+ "source": [
+ "You can learn more about the output utility and the options system in the [User Guide](../user_guide/03-Customizing_Plots.ipynb)."
]
},
{
