I meant:
$T(spec.elementId).autocompleter.url += "?" + "selected=" +
selected_option;
On 05/01/2013, at 9:14 PM, Geoff Callender wrote:
> Autocomplete adds a bit of javascript to the client:
>
> $T(spec.elementId).autocompleter = new
> Ajax.Autocompleter(spec.elementId, spec.menuId, spec.url, spec.config);
>
> Perhaps you could add some javascript of your own that watches for changes in
> the Select, and appends the selected option to the url as a query parameter.
>
> $T(spec.elementId).autocompleter.url = "?" + selected_option;
>
> In your PROVIDE_COMPLETIONS handler you'd get the query parameter, using
> either @ActivationRequestParameter or Request#getParameter(String name).
>
> Geoff
>
> On 05/01/2013, at 3:55 AM, Taha Siddiqi wrote:
>
>> If autoComplete was having a context parameter you could have used the
>> context. :)
>>
>> something I have done here
>>
>> http://tawus.wordpress.com/2012/11/25/tapestry-and-editable-for-bootstrap/
>>
>> regards
>> Taha
>>
>> On Jan 4, 2013, at 10:13 PM, Thiago H de Paula Figueiredo wrote:
>>
>>> On Fri, 04 Jan 2013 13:19:51 -0200, Stephan Windmüller
>>> <stephan.windmuel...@tu-dortmund.de> wrote:
>>>
>>>> Hi!
>>>
>>> Hi!
>>>
>>>> Unfortunately this does not work as expected. Even when the field is
>>>> marked for flash persistence, the "provideCompletions" event is only
>>>> able to read the value once, after that it is null.
>>>
>>> That's exactly what the flash persistence is supposed to do: once read, the
>>> value is removed from the session.
>>>
>>>> Is there a "best way" to store changes made by AJAX requests in the page?
>>>
>>> Have you tried non-flash session persistence and setting the field to null
>>> after you don't need it anymore?
>>>
>>> --
>>> Thiago H. de Paula Figueiredo
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>>> For additional commands, e-mail: users-h...@tapestry.apache.org
>>>
>>
>
