Skip to content
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

fileInput bypass submitButton behavior #45

Closed
yannrichet opened this issue Nov 26, 2012 · 6 comments
Closed

fileInput bypass submitButton behavior #45

yannrichet opened this issue Nov 26, 2012 · 6 comments

Comments

@yannrichet
Copy link

yannrichet commented Nov 26, 2012

Trying to use in the same ui a submitButton and a fileInput, it seems that when a file selection is done, the submitButton is not taken into account, that is to say, the output are processed immediatly.

Even if it could be taken as a bug, I think it should be more convenient to have an explicit event handling method for the submitButtton.
Something like a boolean which says if the last event was the press on this button (false if it was any other widget which was updated) ... But I don't know if it is possible with the shiny events policy...
It should also allow to use several buttons on the same ui.

Best regards,
Yann

@HarlanH
Copy link

HarlanH commented Nov 27, 2012

See this thread: button that's not a submitButton

@yannrichet
Copy link
Author

Yes, you are right
And even, a more standard version of such button is available in shiny-incubator git

Nevertheless, the bug of submitButton+uploadFile remains, so I don't close the issue

@biwa7636
Copy link

+1 fileinput bypass submitbutton

@dasternberg
Copy link

+1 for this.

@coatless
Copy link

coatless commented Apr 1, 2016

Any eta on this functionality being addressed?

@jcheng5
Copy link
Member

jcheng5 commented Apr 4, 2016

submitButton edge case bugs are generally unlikely to be fixed; we'd deprecate that feature if we thought we could get away with it, as its overall design is flawed, making it susceptible to lots of bad edge cases.

The actionButton/eventReactive/observeEvent family of functions are far superior, though there is a bit more up-front learning to do.
http://shiny.rstudio.com/articles/action-buttons.html

@jcheng5 jcheng5 closed this as completed Apr 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants