Leandro, For refresh_on_change to work you need a set of optional selections and a set of refresh_on_change values, so in your example, the type should probably be a select instead of data. You'll also need the select list options to be generated based on your history items (at least that's what I think you're attempt here), so your list of refresh_on_change values will be attributes of those history items.
Greg Von Kuster On Mar 21, 2012, at 9:27 AM, Leandro Hermida wrote: >> >> Here's one example: >> >> <inputs> >> <param type="data" name="dataset" refresh_on_change="true" >> label="Select a file from you history" /> >> <param type="select" multiple="true" name="dataset_values" >> dynamic_options="get_options_from_file(dataset.file_name)" /> >> </inputs> >> >> If the user changes their selection of data from their history it >> should refresh the page and call the dynamic options again to load the >> other select menu with the choices from the new file. Currently you >> have to do this with repeat or pages tags which is really cumbersome >> for the user in the UI or doesn't allow workflowing, respectively. >> >> >> Page should refresh automatically when dataset is changed and dynamic >> options are used. If not, it's a bug. > > Ok, not sure what this means, the above example I wrote doesn't work > so is this a bug or is there another way to write the above example so > that it will work? > > regards, > Leandro > >> > > ___________________________________________________________ > Please keep all replies on the list by using "reply all" > in your mail client. To manage your subscriptions to this > and other Galaxy lists, please use the interface at: > > http://lists.bx.psu.edu/ >
___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
