MathGroup Archive 2010

[Date Index] [Thread Index] [Author Index]

Search the Archive

Re-virginating Manipulates?

  • To: mathgroup at
  • Subject: [mg114256] Re-virginating Manipulates?
  • From: AES <siegman at>
  • Date: Mon, 29 Nov 2010 06:06:33 -0500 (EST)

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>>
      <<Header cell>>
      <<Header cell>>
      <<Header cell>>

What initial cells does each demo_x need to make that demo execute as a  
virgin demo when jumped to?]

  • Prev by Date: Re: to get all parametric plots/line traces
  • Next by Date: Re: How to short-circuit match failure?
  • Previous by thread: Re: Pass by reference for compiled functions
  • Next by thread: Re: Re-virginating Manipulates?