-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/wireframe #422
Feature/wireframe #422
Conversation
…gine option to the clear3d() which results in an error being raised. Can be reproduced as ``` nclear3d() plot3d(Cell07PNs[[2]],col='blue',add=F) ```
…cases for the same.
@jefferis Thanks for this, I see your point, isn't it usually the convention that when a function has one formal argument, followed by ellipsis, people usually can supply that argument without naming them, or to frame it better which is usually preferred, |
It's because |
Things that still need to be done:
|
available with `methods(wire3d)`. * Updated wordlist for spelling. * Cleaned up code.
@jefferis: I have updated all the comments per our discussion, please review this and merge the same. |
R/wire3d.R
Outdated
#' options(nat.plotengine = 'plotly') | ||
#' wire3d(kcs20.mesh,alpha = 0.1, col = 'blue') | ||
#' } | ||
wire3d <- function(x, ..., add = FALSE, plotengine = getOption('nat.plotengine')) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be add=TRUE
to be consistent with current usage (where wire3d doesn't clear the plot)
Thank you! |
Updated for #421
@jefferis:
which can be reproduced as follows:
wire3d
that masks the function with the same name fromrgl
and will pass the call to eitherrgl
orplotly
dependent on the option ofnat.plotengine
.