Description of the limitation and why it is relevant to address
As a Developer I want to have a button that is able to set params after performing a download so that I have the option to have 1 button instead of two
I think this is relevant for the VIKTOR platform because it adds more flexibility and less button presses.
use_cases
- Download a file, and set a hiddenfield to retrigger a view (set_params via the api will not work: it will not retrigger the front-end)
- Download a file and reset certain parameters to a default/empty state
- Download a file and store the results for a later step (this actually can be done with the API, but see below)
Submitter proposed design (optional)
I would like to have a DownloadAndSetParramsButton. Additional to the current DownloadResult the class should consume a params object –> After the download is completed the params are set to the given values (actually a combination of the current two separate buttons)
Current workarounds
Currently it is not really possible to do this. When doing a download we could include a set_params call to de API –> the issue is that the params are not reflected on the front-end –> only after a manual refresh. A SetParamsResult does refresh the result, so I feel that all ingredients are already there, but there should be a combination of the Download and SetParams button. I could not find a workaround to get both of them working.