Skip to content
Snippets Groups Projects
Commit 88afbee5 authored by Christophe Geuzaine's avatar Christophe Geuzaine
Browse files

explain that "Duplicata View[i]" does not actually copy the data
parent 08733c1d
No related branches found
No related tags found
No related merge requests found
\input texinfo.tex @c -*-texinfo-*- \input texinfo.tex @c -*-texinfo-*-
@c $Id: gmsh.texi,v 1.135 2004-10-08 04:36:21 geuzaine Exp $ @c $Id: gmsh.texi,v 1.136 2004-10-12 17:21:06 geuzaine Exp $
@c @c
@c Copyright (C) 1997-2004 C. Geuzaine, J.-F. Remacle @c Copyright (C) 1997-2004 C. Geuzaine, J.-F. Remacle
@c @c
...@@ -2268,6 +2268,13 @@ post-processing view numbers start at 0. ...@@ -2268,6 +2268,13 @@ post-processing view numbers start at 0.
@item Duplicata View[@var{expression}]; @item Duplicata View[@var{expression}];
Duplicates the @var{expression}-th post-processing view. Duplicates the @var{expression}-th post-processing view.
Note that @code{Duplicata} creates a logical duplicate of the view without
actually duplicating the data in memory. This is very useful when you want
multiple simultaneous renderings of the same large dataset (usually with
different display options), but you cannot afford to store all copies in
memory. If what you really want is multiple physical copies of the data,
just merge the file containing the post-processing view multiple times.
@item Plugin (@var{string}) . Run; @item Plugin (@var{string}) . Run;
Executes the plugin @var{string}. The list of default plugins is given in Executes the plugin @var{string}. The list of default plugins is given in
@ref{Post-processing plugins}. @ref{Post-processing plugins}.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment