Re: "Freezing" an Output cell?
- To: mathgroup at smc.vnet.net
- Subject: [mg103708] Re: "Freezing" an Output cell?
- From: Hannes <HannesKessler at hushmail.com>
- Date: Sat, 3 Oct 2009 09:02:43 -0400 (EDT)
- References: <firstname.lastname@example.org>
Hello, here is one possible way: Select the cell, type ctrl+shift+o to invoke the option inspector, type GeneratedCell or CellAutoOverWrite followed by Enter in the Lookup field, set both options to False. CellAutoOverWrite = False prevents overwriting the cell when a preceeding input cell is executed, GeneratedCell = False prevents deleting the cell by the menu command Cell -> Delete all output. Another way is to type Deletable in the option inspector followed by Enter twice and set this option to False. Obviously you cannot cut and paste the cell afterwards. Best regards, Hannes Kessler On 2 Okt., 14:25, AES <sieg... at stanford.edu> wrote: > I'd like to understand the recommended way(s) to "freeze" an Output cell > created and displayed in a Mathematica notebook, so that one can delete > the Input cell(s) that created it and the Output cell remains as a > permanent "Text-like" cell in the notebook, visible to readers, and not > deleted by subsequent Cell >> Delete All Output menu commands. > > Example: In the opening section of a notebook addressing some physical > problem I create a Graphic displaying the geometry and coordinate > systems associated with the problem, and maybe a Table displaying some > of the variable names I'll be using and some (possibly derived) > numerical values. > > Hopefully, at some point, once I've gotten off to a good start, I can > delete the code that creates these displays, and not have to re-execute > them further, just retain the Output cells, essentially unchanged in > appearance. How to do this? > > [And is there a better name than "freezing" for this process?] > > For myself, I'd prefer a point and click method, e.g., choose a new > Style for these Output cells using the Format >> Style menu, over having > to put some special code in the Input cells that create them. But, > others may differ. > > Thanks for any suggestions.