-
Notifications
You must be signed in to change notification settings - Fork 1
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
extra.vars
functionality a la dittoSeq
#20
Comments
It already works to where every column is kept, and embedded:
But I've found with real data that there can be a LOT of lag from the complete lack of data trimming in scatterPlot and yPlot, so I agree that an |
I may just be a dunce with ggplot, but it took me a second to figure out how the data can be accessed from the plot object itself, e.g.
I tried a few approaches before finding the appropriate ones:
Just commenting this here for my own sake. |
mmmm, this still gives me more inspiration lol I suppose there could be some increased consistency over whether the plot is given a default The faceting in my example worked because it operates on the plot layers, but there could be some default data setup picked for all plots that is given in the top-level call, |
Yeah, in my case, I was trying to use it for plotly stuff downstream, so when |
This functionality is convenient in a lot of ways. Looking at
dittoSeq
, the data collection is pretty complicated. I haven't toyed with it here, but I assume it'd just be tweaking the.data_adjust_scatter
function to pop them on as well.I know one can use
data.out
to get the full data, but it being embedded in the plot object was handy in its own way.The text was updated successfully, but these errors were encountered: