Overlaying subplots when using plotProxy()/plotlyProxyInvoke() in Shiny App
Personne n'a encore pris cette issue.
- Langage dominant
- R
- Étoiles
- 2.7k
- Forks
- 641
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
I was hoping to extend the plotly.R "relayout" shiny example found here to incorporate a subplot of 3 figures with a range slider down the bottom. Here is what I tried:
library(shiny)
library(plotly)
ui <- fluidPage(
plotlyOutput("plot")
)
server <- function(input, output, session) {
p <- txhousing %>%
group_by(city) %>%
plot_ly(
x = ~ date,
y = ~ median,
mode = 'lines',
type = 'scatter',
source = 'myplot'
) %>%
rangeslider(thickness = 0.05)
output$plot <- renderPlotly({
# Just duplicating plots for this example
subplot(p, p, p, shareX = T, nrows = 3) %>%
layout(height = 720)
})
observeEvent(event_data("plotly_relayout", source = "myplot"), {
d <- event_data("plotly_relayout", source = "myplot")
# unfortunately, the data structure emitted is different depending on
# whether the relayout is triggered from the rangeslider or the plot
xmin <- if (length(d[["xaxis.range[0]"]])) d[["xaxis.range[0]"]] else d[["xaxis.range"]][1]
xmax <- if (length(d[["xaxis.range[1]"]])) d[["xaxis.range[1]"]] else d[["xaxis.range"]][2]
if (is.null(xmin) || is.null(xmax)) return(NULL)
# compute the y-range based on the new x-range
idx <- with(txhousing, xmin <= date & date <= xmax)
yrng <- extendrange(txhousing$median[idx])
plotlyProxy("plot", session) %>%
plotlyProxyInvoke("relayout", list(yaxis = list(range = yrng)))
})
}
shinyApp(ui, server)
Below is a preview of the plotly output before using the rangeslider:

And here is the resulting plotly output after I use the rangeslider:

I have also tried replacing:
plotlyProxy("plot", session) %>%
plotlyProxyInvoke("relayout", list(yaxis = list(range = yrng)))
With this instead:
plotlyProxy("plot", session) %>%
plotlyProxyInvoke("relayout", list(yaxis = list(range = yrng),
yaxis2 = list(range = yrng),
yaxis3 = list(range = yrng)))
...just in case I was able to independently control the individual y-axes of the subplot. However, this didn't work either. The
original example works great for the single plot; it is when I try adding in the subplots that things get whacky.
I was wondering if anyone else can confirm this plotting behaviour? Any suggestions for a workaround?
Thanks in advance! :)
[UPDATE]
I managed to find a workaround. The issue seemed to be that when calling the plotProxy()/plotProxyInvoke() functions the subplot domains got garbled :-S. However, if I explicitly set the domains for each y-axis (roughly breaking the vertical real-estate in thirds) in then everything displays as it should:
plotlyProxy("plot", session) %>%
plotlyProxyInvoke("relayout", list(yaxis = list(range = yrng, domain = p$x$layout$yaxis$domain),
yaxis2 = list(range = yrng, domain = p$x$layout$yaxis2$domain),
yaxis3 = list(range = yrng, domain = p$x$layout$yaxis3$domain)))
where the object p is the original plot_ly obj that I am able to access on the server side.
Any idea why the calling plotProxy()/plotProxyInvoke() seems to garble the original y-axis domains? The workaround does solve the problem, just feels a bit clunky to have to do that each time the rangeslider updates.
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Piste de recherche
Commencez par inst/examples/shiny/proxy_relayout/app.R, puis reproduisez l’exemple de subplot à trois panneaux en utilisant subplot(), plotlyProxy() et plotlyProxyInvoke("relayout"). Étudiez pourquoi relayout modifie les domaines de l’axe y du subplot, notamment dans les cas yaxis, yaxis2 et yaxis3. Le travail est terminé lorsque le rangeslider met à jour les plages de y sans obliger les appelants à restaurer manuellement le domaine de chaque axe.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- r
- Domaine
- data-visualization
- Type d'issue
- Bug
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 45/100