At the time of writing, some visualizations in Displayr are too slow (:()). We understand why and are doing a lot of work to fix this. One of the reasons they are slow is that they are run by creating calculations in the background. You can verify this by selecting a visualization and seeing if there is an R CODE group in the Properties tab of the object inspector. For example, you can see the code for a pictograph below.
A simple hack for speeding things up is to place any calculation code at the beginning of this R CODE. However, if you do:
- Please do it as a last resort. It's fiddly.
- Email firstname.lastname@example.org if you can't figure out how. Make sure you tell them the specifics, as it's a complicated enough area that it's not possible to write a useful general article with instructions.
A safer and more sophisticated way of doing this is to create the tables and visualizations by writing code into your calculations. For example, you can create a custom formatted table using the