Re: Re-virginating Manipulates?
- To: mathgroup at smc.vnet.net
- Subject: [mg114300] Re: Re-virginating Manipulates?
- From: Herman Kuun <oomkoos1 at gmail.com>
- Date: Tue, 30 Nov 2010 04:05:13 -0500 (EST)
One suggestion:- Remove["`*"]; demo_a (* Cell one *) Remove["`*"]; demo_b (* Cell two *) : : Remove["`*"]; demo_last (* Cell last *) Best Herman On Mon, Nov 29, 2010 at 1:06 PM, AES <siegman at stanford.edu> 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?] > >