[Date Index] [Thread Index] [Author Index]
Re: Re-virginating Manipulates?
In the Cell menu, "Delete All Output" will get rid of all of the output, print, and message cells, which goes a long way toward what you want. Of course, there may be latent kernel state which you'll need to flush. And the only absolutely sure way of doing that is to quit the kernel. Evaluation->Quit Kernel->Local will do it, or you can just evaluate Quit in a new cell. Sincerely, John Fultz jfultz at wolfram.com User Interface Group Wolfram Research, Inc. On Mon, 29 Nov 2010 06:06:33 -0500 (EST), AES wrote: > Let's define the label "virgin" for a Mathematica notebook as referring > to the condition and content of a notebook file that's been opened for > the first time, had some cells typed into it, maybe been Saved, but none > of its cells have ever been executed. > > How can one re-virginate such a notebook (and also the currently > running Mathematica app and kernel, if necessary) after any (or all) of > the cells in this notebook have been executed one or more times -- > especially if the notebook contains one or more Manipulates? > > [If you want more detail, the objective is to code a number of > (potentially multi-cell) "demos" -- call them demo_a, demo_b, ... -- > each of which contains a Manipulate, and all of which are totally > independent of each other (no transfer of info between different demos > needed or wanted); and then be able to jump around randomly amongst > these demos, executing or re-executing them, and getting identical > results each time a given demo is executed, regardless of what's > happened before it is selected and executed. > > Each demo is, preferably, a separate notebook (a separate file), or > multiple demos could be cascaded in a single notebook, in the form > > <<Header cell>> > demo_a > <<Header cell>> > demo_b > <<Header cell>> > demo_c > <<Header cell>> > > What initial cells does each demo_x need to make that demo execute as a > virgin demo when jumped to?]