You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I dislike argument bloat, but based on d3treeR/d3treeR#12 from d3treeR, would it be possible to add an argument to skip the grid drawing piece in lines. Using the contrived example from d3treeR/d3treeR#12 with 4000 rows, here is the lineprof view.
I hesitate to even ask since treemap was designed for output, but would it be possible to add an argument to skip the plotting for use with d3treeR or other potential piggybacking packages?
The text was updated successfully, but these errors were encountered:
Sure, no problem! Please try the latest version. It's a quick and dirty solution though: it still generates a grid.newpage(), with all its viewports. I cannot simply ignore that, since this also results in the aspect ratio that is needed to run the rectangle placement algorithm. A more elegant solution would be to let the desired aspect ratio be determined by the user in case draw=FALSE.
This is great. Sorry been really sick all week so just getting a chance to check it out. I'll use grid.grep to look for a legend in d3treeR so we know either a legend was not drawn or draw = FALSE. However, would it be worthwhile to add the value of draw in the invisibly returned list. Happy to submit pull if you would like.
I dislike argument bloat, but based on d3treeR/d3treeR#12 from
d3treeR
, would it be possible to add an argument to skip thegrid
drawing piece in lines. Using the contrived example from d3treeR/d3treeR#12 with 4000 rows, here is thelineprof
view.I hesitate to even ask since
treemap
was designed for output, but would it be possible to add an argument to skip the plotting for use withd3treeR
or other potential piggybacking packages?The text was updated successfully, but these errors were encountered: