show_if variation

[willking98]

Description

I think the show_if function is working slightly differently when used in conjunction with sd_question and sd_output. For me, I have to click next in order to render the conditional question when using sd_output whereas when using sd_question the conditional question pops up instantly when the condition is satisfied (once correct option has been selected). I think this might be a speed issue as sometimes it renders and other times I have to click next.

[jhelvy]

Can you provide a quick demo? like a simple survey.qmd and app.R where this happens?

[jhelvy]

Okay I can reproduce this. In this example the hidden question won't show at all when you choose "other" on the first question:

survey.qmd:

---
format: html
echo: false
warning: false
---

```{r}
library(surveydown)
```

::: {#page1 .sd-page}

```{r}
sd_question(
  type  = 'mc',
  id    = 'penguins',
  label = "Which is your favorite type of penguin?",
  option = c(
    'Adélie'    = 'adelie',
    'Chinstrap' = 'chinstrap',
    'Gentoo'    = 'gentoo',
    'Other'     = 'other'
  )
)

sd_output(id = 'penguins_other', type = 'question')

sd_next()
```

:::

::: {#end .sd-page}

## This is the end of the demo survey showcasing the conditional display feature.

```{r}
sd_close()
```

:::

app.R:

library(surveydown)

server <- function(input, output, session) {

  sd_question(
    type  = "text",
    id    = "penguins_other",
    label = "Please specify the other penguin type:"
  )

  sd_show_if(
    input$penguins == "other" ~ "penguins_other"
  )

  sd_server()

}

shiny::shinyApp(ui = sd_ui(), server = server)

[willking98]

I think my conditional questions are showing because of all_questions_required = TRUE. You should be able to see what I mean by running the survey I have developed here

[jhelvy]

Okay I just pushed a patch. Try reinstalling and see if this works:

remotes::install_github("surveydown-dev/surveydown", force = TRUE)

[willking98]

Works perfectly, nice work. Cheers!

[jhelvy]

Such a small little bug. Thanks for the quick notice. We tried to make sure everything was still working after making such big changes to the architecture. One more thing we noticed is the little red asterisk for required questions won't show on questions defined in the server. The required feature still works, but the question label is just missing the red asterisk. We'll have it patched soon.

[willking98]

No problem at all. Thanks for getting it sorted so quickly.

The other thing I wanted to mention which seems to have changed in this update is the formatting of mc_buttons see images below. Is it still possible to use the old formatting? Also is it possible to force each option to appear on a new line?

New

Old

[jhelvy]

Ah, good catch. @pingfan-hu can you take a look at this?

By moving from a Quarto shiny document to now just a regular Quarto doc + a shiny app, we lost some of the nice formatting that Quarto handled for us. Pingfan has been working on the UI to try and make things looks similar to how they rendered before.

[pingfan-hu]

I didn't intentionally modify the buttons. The old layout has equal width because quarto renders it this way. Now since it becomes a Shiny app, it's rendered differently. I'll see if I can do something in the css or insert some JS codes.

[pingfan-hu]

Hi @willking98 , I've solved your problem. You can see the screenshot here:

This is done by defining the direction parameter as "vertical" in mc_buttons. This parameter is available for both mc_buttons and mc_multiple_buttons, default to "horizontal".

For your convenience, I've modified all your mc_buttons questions to have vertical alignment:
demo-choice-based-conjoint-modified.zip

Another parameter is called "width". You can define it as "400px" or "80%" so that you can control the width of the question container, which then affects the box length. The texts will automatically wrap if they are too long, like this:

Please update our package and try it:

remotes::install_github("surveydown-dev/surveydown", force = TRUE)

Now we have a bug that if you define width as 80%, the question container will take 80% of the page width, but then the button width will be 80% of the container, making the button width being 64% of the page. I will fix it later.

[pingfan-hu]

@willking98 As a follow-up, the width problem has been solved. Now if you define a width value to your questions, say "80%", "60%", etc., only the question container will shrink, but the buttons will still fully span.

[willking98]

Brilliant, that now works really well. Thanks @pingfan-hu!