No handler registered for type ..:actionButton [0.10.2.9001]

269 views
Skip to first unread message

Chris B.

unread,
Oct 14, 2014, 5:20:51 AM10/14/14
to shinyap...@googlegroups.com
This error is reproducible and occurs with the latest changes to shiny.

Running the example of observeEvent() or eventFilter() gives the following error:

Error in handler(binary, message) :
 
No handler registered for for type saveButton:actionButton

That said, all previous shiny apps utilising actionButton() in "legacy mode" (i.e. as in the example of actionButton()) return the same error and stop working as soon as a button is pressed.


Example of observeEvent()
## Not run:
# In ui.R:
shinyUI
(basicPage(
  numericInput
("n", "Number of observations", 5),
  actionButton
("saveButton", "Save")
))
# In server.R:
shinyServer
(function(input, output) {
  observeEvent
(input$saveButton, function() {
    write
.csv(runif(input$n), file = "data.csv")
 
})
})


## End(Not run)


Session info
> sessionInfo()
R version
3.1.1 (2014-07-10)
Platform: x86_64-w64-mingw32/x64 (64-bit)


locale
:
[1] LC_COLLATE=English_United Kingdom.1252  LC_CTYPE=English_United Kingdom.1252    LC_MONETARY=English_United Kingdom.1252
[4] LC_NUMERIC=C                            LC_TIME=English_United Kingdom.1252    


attached
base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base    


other attached packages
:
[1] shiny_0.10.2.9001


loaded via a
namespace (and not attached):
 
[1] devtools_1.6.1  digest_0.6.4    htmltools_0.2.6 httpuv_1.3.0    httr_0.5        mime_0.2        R6_2.0          Rcpp_0.11.3     RCurl_1.95-4.3
[10] RJSONIO_1.3-0   stringr_0.6.2   tools_3.1.1     xtable_1.7-4  



Fereshteh Karimeddini

unread,
Oct 14, 2014, 10:52:55 AM10/14/14
to shinyap...@googlegroups.com
Chris,

Thanks for reporting this issue. I opened this ticket for the issue.

For future, if you run into issues or questions about Shiny package, it would be better to post them to this forum:



Best,
Fereshteh

Joe Cheng

unread,
Oct 14, 2014, 12:26:34 PM10/14/14
to shinyap...@googlegroups.com
My fault, bad merge yesterday. It's fixed now.

Thanks for the report, Chris!
Reply all
Reply to author
Forward
0 new messages