Hi Eric,

I'm making a start on that idea of cascading the selection from one 
*<<combobox>>* into the filter for the options of another. However, in the 
second example on this experiment tiddler 
<https://tiddlytest.github.io/#Playing%20with%20Eric%27s%20combobox%20and%20the%20%22okaction%22%20param>,
 
I'm stuck with a bit of a problem. Despite having specified field:"city" as 
the field from which the *option value* should be stored, it still seems to 
be storing the title of the selected option, rather than the city. The *option 
labels* are being populated properly, using your example above of 
template:"{{!!city}}", but the *option values* aren't respecting the field: 
parameter.

Thanks in advance,

Hegart.


On Thursday, 7 April 2016 19:34:41 UTC+12, Eric Shulman wrote:
>
> On Wednesday, April 6, 2016 at 11:48:43 PM UTC-7, Hegart Dmishiv wrote:
>>
>> We've run into a little snag with the *goaction* parameter. We can't 
>> seem to get it to work, neither in your example in the documentation 
>> <https://tiddlytools.github.io/InsideTW/empty.html#TiddlyTools%2FMacros%2Fcombobox%2Finfo>,
>>  
>> nor in our own experimental tiddler 
>> <https://tiddlytest.github.io/#Playing%20with%20Eric%27s%20combobox%20and%20the%20%22goaction%22%20param>.
>>  
>> Any idea what's going on? This is something we'd really like to use, for 
>> all sorts of purposes in our TiddlyCRM project.
>>
>
> If you specify field:"text" in the macro call, it works.
>
> Originally, the macro had a default field name of "text" automatically 
> assigned as a fallback.  However, this prevented the underlying $edit-text 
> widget from being able to handle set of values in data tiddlers (using 
> index:"..."), because the field:"..." param takes precedence if not left 
> blank.
>
> Note: the documentation was also incorrect in using the "list" param, 
> which was renamed "filter" (but you apparently found that on your own, 
> since your experiment is correctly using filter:"..."
>
> Also... although you correctly used the "okaction" param in your 
> experiment, in your posting here, you called it "goaction".  I just want to 
> make sure others reading this don't get confused by the mistaken param name 
> in the message.  Also note that, separate from the "okaction" is an 
> optional (and currently undocumented) "clickaction" param, which allows you 
> to extend the default action that occurs when you click an item in the list 
> (i.e., in addition to setting the clicked item value into the edit-text 
> field, you can have other "side-effect" actions performed when the item is 
> clicked).
>
> enjoy,
> -e
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/f6f47721-96c1-4550-a475-8dc10f0cdadb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to