cerulean | Node.js QWERTY instrument

Please use the following to check if the ragg output remains identical on your system and shinyapps.io:

It works fine with fluidPage(). Not sure why it does not work with pageWithSidebar() for your code. Try this

There's a few things going on here.

First, I think the biggest piece is that the input$checkGroup returns the values in the selection list, not the labels/names displayed to the user. It also returns this value as a string, i.e. when the user selects "Solar", the server will see an input value of "1".

Second, your Data variable needs to be a reactive. Right now your if/else statement will be executed at launch and never again. Since you don't specify an initial selection, the input value will be NULL not matching any of the conditional statements, and no value will be assigned to Data.

I would do something along the lines of this. Load your data sets into a static list (this will prevent reads from disk every time the user adds/removes checks)

Did this with HTML tags while trying to mimicking the HTML DOM structure and element classes just the way Shiny would create them.

Two 6-width column elements within a 12-width column to put the content side by side. I did not change much inside each column.

I think your warnings are due to input$timestamp being NULL the first time in your reactive expressions, before you create the dateRangeInput.

You could move your input to ui, and then use updatePickerInput when the dates change to alter your other inputs accordingly.

You might want to include two separate reaction expressions. One for filtering the data based on the date range, which will be used to update the other pickers. The second will include the other filters for location, equipment, and weekday, based on the picker selections.

See if this provides something closer to what you are looking for. I included what seemed to be the relevant packages at the top. I also adjusted your parentheses in the ui a bit.

This sample app shows how it can be done.

• Your idea using selecizeInput was correct. However, I would not recommend declaring the data frames as global variables. The usual approach would be to keep the data in the server and feed only the data we want to show to the client.
• Use updateSelectizeInput to set the choices once the data frames have been loaded. The observerwill do that every time dfchanges.
• Finally, renderTablefilters the relevant part of the data frame and sends it to the client.

You almost got it. I think you missed adding Sidewalk_Condition in the outcome update_role function.

Try this:

Perhaps you want to try actionBttn.

You have done too much before realizing that it did not work.

• radio button cannot be styled the way you tried, but can be hidden
• to toggle selection in between radio , but keep only one checked, they need to have the same name value ( meaning that they are a group where only one can be checked) and have a different id
• + selector is fine, but opacity :0; keeps elements in the flow, (why not, but only one can be seen and your radio can be bothed checked :( )
• negative margin can be a way to mind the height of every tabs, but it is clumsy somehow. lucky we are nowdays with grid, many children can share the same cell without the use of absolute.
• inputs ahead the container to hide/show is just fine for the selector +, but you also got the ~ selector that might allow you to group your inputs together (readability of the code ) but like you did is also fine and reduce the selector to use to a single one.grouping the inputs ahead befor the label could allow to style the labels too

for example what you could have done with the same name value for inputs but differents id and grid something working (not highlighting the current label ):