Plot.Clear() doesn't clear everything
See original GitHub issueThis is a good example of a bad software pattern. Switch statements don’t get updated when new pottables are added.
This hack works to clear experimental plottables (relates to #249):
wpfPlot1.plt.GetPlottables().Clear();
Perhaps Clear should only have two simple overloads:
Clear()
to clear allClear(Type)
to clear just that plottable type
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
How To Clear A Plot In Python (without closing the window)
The matplotlib.pyplot.cla() function clears the current Axes state without closing the Axes. The elements within the Axes are not dropped ...
Read more >How to clear memory completely of all matplotlib plots
from matplotlib import pyplot as plt f = plt.figure() f.clear() ... that creates 100 figures then attempts to delete them all from memory:...
Read more >Plot.Clear() doesn't clear everything · Issue #275 · ScottPlot ...
Switch statements don't get updated when new pottables are added. This hack works to clear experimental plottables (relates to #249):. wpfPlot1.
Read more >How to clear the memory completely of all Matplotlib plots
How to clear the memory completely of all Matplotlib plots? · close() by itself closes the current figure · close(h), where h is...
Read more >MATLAB clf - Clear figure
clf('reset') deletes all children of the current figure regardless of their handle visibility. It also resets the figure properties to their default values, ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for bringing this to my attention! I’ll prioritize fixing this and getting it on NuGet.
Something like:
(let me know if that does the trick)
released in 4.0.24