compositions (version 1.40-2)

replot: Modify parameters of compositional plots.

Description

Display only a subset of the plots.

Usage

replot(...,dev=dev.cur(),plot=TRUE,envir=NULL,add=FALSE)
replotable(expr,add=FALSE)
noreplot(expr,dev=dev.cur())

Arguments

expr

A (unquoted) expression that does the plotting. replotable will make the generated plot replotable and noreplot will do the inverse and avoid that the plots overwrites the current database entry.

...

Plot parameters to be modified. E.g. onlyPanel

dev

The device that currently contains the plot. It will be plotted in the current device.

plot

logical or call or list of calls. If plot is TRUE, the new version of the plot is plotted in the current environment (and typically stores itself here). If plot is FALSE the modified plot is simply stored, rather than actually plotted (in its own old plotting environment). If the parameter is something else, it is stored to the internal plot database for the given device (but not plotted or evaluated).

envir

a new enviroment to be assigned to the plot. Rarely needed.

add

either a logical to indicating that the plot adds something to the plot. Or a number / name of the added thing to be modified.

Value

replot returns an invisible copy of the modified call. replotable and noreplot return the result of expression.

Details

Some of the plot routines of compositions internally store their call as a mean for replaying the plot when information is added or parameters are modified. The stored call can be modified by this function, which pretty much works like a simplified version of update.

replot allows to redo the plot typically in a different device or with different parameters. The function provides this functionallity at a totally different level than dev.copy and allows for the modification of high level parameters on the fly.

Plots can be stored in the internal database by calling replot with a parameter plot set to the call of that plot. Plotting functions without this functionallity can be filtered through replotable(). However in this case all parameter names should be given explicitly.

There are actually three levels of possible replay: The dev.copy level on which graphic actions are replayed. The gsi.pairs function level that organizes panels plots and uses an internal replotting facility to allow modification of the parameter, e.g. addings lines .... And than there is the high level of the actual function call generating the plot.

See Also

plot.acomp, plot.aplus, boxplot.acomp

Examples

# NOT RUN {
data(SimulatedAmounts)
plot(acomp(sa.lognormals5))
straight(acomp(c(1,1,1,1,1)),acomp(c(1,2,3,4,5)))
replot(onlyPanel=c(2,3))
oldPlot <- replot(plot=FALSE) # get the plotting call
replotable(plot(x=1:10)) # To make a graphic replottable
replot(col=1:10)
replot(plot=oldPlot)    # Restore the old plot (without plotting)
replot(onlyPanel=NULL)    # View the whole plot again
replot(pch=20)  # Acctually plot it 
replot(col=20)  # since the actual plot is gsi.pairs not a plot.acomp
 
# }
# NOT RUN {
# The following line in  a plotting function stores the plot for replotting.
replot(plot=match.call()) # Store current call as plot 
replot()                  # simply plot once again
replot(dev=otherdev)      # redo a plot from an other device here.
replot(onlyPanel=c(3,4))  # modify the plot (and replot it)
replot(onlyPanel=c(3,4),dev=7,plot=FALSE) # modify a stored plot
# }