New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
swipr not displaying first reactive quote after tabpanel activated from actionButton #46
Comments
Hi Jules! Best, |
Hi Nick, |
It may be. I have built an app before that has multiple tabs with the swipr that still worked but there may be something else going on due to new versions of the various packages. I'd say a copy and paste of a single file shiny app would be best in this issue thread, or both the server and ui files if it's not easy to combine them. |
Hi Nick, Here is my code. I also uploaded the working app to https://jules-bernard.shinyapps.io/greetingproject/. You'll notice that if any category other than 'Encouragement Messages' (the default) is selected from tab 1, the card will appear blank after the switch to tab 2. --
|
Hi Jules, I just got everything loaded and was able to recreate your issue. I'll work on it and get back to you when I figure out what's going wrong. Thanks for the example! Best, |
I have a small shiny app where on tabpanel2 the shinyswipr module displays quotes pulled from a dataframe at random. tabpanel1 contains actionButtons corresponding to columns of the dataframe with each column containing quotes from different writers.
Once the actionbutton is pressed, a quote is selected properly (I can see from the browser that the reactivevalue is updated), and if I simply render the text on panel2 outside of the shinyswipr module the text displays just fine. However, the shinyswipr module doesn't show the first quote (just appears blank), once the first card is swiped away, the second quote appears as expected.
Any ideas why this is happening? As a workaround, is it possible to call the shinyswipr module to swipe away the first card after the actionButton press?
The text was updated successfully, but these errors were encountered: