JohnCoene / cicerone

🏛️ Give tours of your Shiny apps
https://cicerone.john-coene.com
Other
187 stars 7 forks source link

Unable to move to next to screen #6

Closed Kaushikbharat closed 4 years ago

Kaushikbharat commented 4 years ago

First of all the package is really awesome, loved it. Now Coming to the issue I am working on a modular shiny app in which I am unable to move from one screen to another screen. As in we have two tabpanel in ui in that I am unable to move from one tab to another tab.

Can you please help. Thanks in advance.

JohnCoene commented 4 years ago

I've just pushed new arguments to do so. Could you please give it a spin?

It's by no means ideal but it's the only way I see. I added tab and tab_id to the step method so you can specify which tab should be opened/visible when at said step. Note that this means you will need to give tabPanel an id.

Reinstall from Github.

remotes::install_github("JohnCoene/cicerone")

Then try it out, an example below.

library(cicerone)

guide <- Cicerone$
  new()$ 
  step(
    el = "plot",
    title = "Text Input",
    description = "This is where you enter the text you want to print."
  )$
  step(
    "summary",
    "Send the Text",
    "Send the text to the server for printing",
    tab = "summary_tab",
    tab_id = "tabz"
  )

library(shiny)

ui <- fluidPage(
  use_cicerone(), # include dependencies
  h1("tabs"),
  tabsetPanel(
    id = "tabz",
    tabPanel("plot_tab", h2("show plot here", id = "plot")),
    tabPanel("summary_tab", h2("show summary here", id = "summary"))
  )
)

server <- function(input, output){

  # initialise then start the guide
  guide$init()$start()

}

shinyApp(ui, server)
JohnCoene commented 4 years ago

@Kaushikbharat did this help? Might I close this issue?

homebase3 commented 3 years ago

I tried this example as above on Mac and Linux with both the stable and develop versions of the package, and it is no longer working. Specifically, it gets stuck on the first tab and will not allow you to move to the second when you click "next". Can you look into this?

mihirp161 commented 3 years ago

Having same issue as @homebase3

clbenoit commented 2 years ago

Having same issue as @homebase3 and @opendatasurgeon