Thomas Lin Pedersen
Thomas Lin Pedersen
The way the new grid features have been implemented means that it is non-trivial to map aesthetics to e.g. gradients so it is something that will take quite some work...
The standard class for data.frames in tibble is `tbl_df` which do not require dplyr to handle: ```r > class(tibble::as_tibble(mtcars)) [1] "tbl_df" "tbl" "data.frame" ``` https://github.com/tidyverse/ggplot2/blob/ae7fb41d33fd629cddbea484fc37b5f02dea3c41/R/fortify.r#L17 The code you are referring...
Im not sure I understand the issue. The `tbl` class will require dplyr, unless we are using the `tbl_df` subclass. What do you want to achieve by having the dependency...
Hmmm... it is my clear understanding that `tbl` is a virtual class and you shouldn't really have objects that aren't subclasses of it. If you want to make a special...
I'll await Hadley's comments on this, but IMO this is not expected usage. If you simply want a data.frame with nice formatting you create one with tibble, but I may...
Just to clarify (haven't got access to a pc right now). If you create the futures directly using e.g. `multiprocess` these changes does not affect anything?
shinyFiles uses bootstrap 3 so you cannot expect it to work out of the box with bootstrap 4
This must be a tentative yes🤷♂️. I know very little about modelling fluid dynamics but if it can be expressed as a series of discrete steps then particles should be...
This is due to changes in ggraph - I'll try to update the example soon
haven't had time to look into it, but @jsan4christ's solution is generally applicable...