Closed ghost closed 8 years ago
This is unlikely to have anything to do with flexdashboard. @timelyportfolio ?
One thing I noticed is that the parcoords package doesn't implement resize which if not the cause of this problem will result in all kinds of other layout problems within flexdashboard.
@jjallaire, resize
will be a curse to last year's widgets, since I did not implement resize
in many of them. In parcoords
I deliberately avoided because render can be so resource intensive, and since it combines canvas with svg, re-render is the only way to resize.
@carbonmetrics, I'll try to quickly implement resize
, but I'm not positive it will resolve this problem. I will say that I don't think RColorBrewer
has any part in this. I also don't think it is flexdashboard
. Based on my experience, I would say tabset
is the source of this trouble. There are lots of dependencies and asynchronous behaviors at play here, so as you say, debugging can be a nightmare.
@timelyportfolio Thanks! That would be great. I use parcoords all the time, my clients all go wild when they see it/get it. I indeed noticed that removing tabsets and pages solved the misbehaviour.
The life of a htmlwidget
developer gets harder and harder.
@carbonmetrics, I just started work on this. Will you please help me test?
devtools::install_github("timelyportfolio/parcoords@feature/resize")
@timelyportfolio, I have made a flexdashboard with different layouts and uploaded it to rpubs.
As long as you switch autoresize=T it will work, also with tabsets. The problem (it seems to me) is valueboxes. The parcoord size gets stuck if you use them, also if you try to adjust data-width or data-height. Something similar is happening with d3heatmap.
The life of a htmlwidget developer is probably indeed getting harder and harder, so I will try to get you a picture of someone who is using this widget for the first time here in Nairobi, Kenya.
The combination of RColorBrewer with parcoords and (new) page leads to a blank parcoords chart - sometimes. It's hard to reproduce because it is so irregular (regular enough to pull your hairs out). If it occurs then the rendered result opens at page 3 instead of page 1. When going to page 1, this is what you see:
Test script: