Hi Scott
No problem. The filter syntax is all standard — nothing unusual for the
ActionListops widget. There’s documentation on filter expressions and filter
runs on tw5.com — takes a little getting used to though. I investigate filter
expressions in the filter tab of advanced search — helps to
Ah, I see now. (I think.)
I wasn't recognizing the value of $tags as a filter expression. Viewed in
that light, the *+* makes a little more sense.
Though it does prep my brain to expect that any string passed in there
*without* the *+* would overwrite the existing tags entirely. I.e., if
$t
Hi Scott
This isn't a special meaning -- only that the $tags= and $subfilter=
attributes of the widget are set up to operate on the existing content of
the target field (as additional filter runs.)
So:
<$action-listops $field="my-field" $subfilter="+[additional[filter run]]"/>
Is equivalent to
Ohh!
I was unaware of the special meaning *+* has in <$action-listops>.
Even cooler! :D
--
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 tiddlywiki+unsubscr.
Hi Scott
If you examine the logic:
-- '+[prefix[$:/]]' keeps items prefixed with '$:/" (and discards all other
items)
-- and '+[!prefix[$:/]]' keeps items not prefixed with '$:/" (and discards
the system tags)
regards
On Thursday, 14 January 2016 08:12:52 UTC+2, Scott Simmons (Secret-HQ) wrote
*VERY *cool. I had no idea you could pass filter expressions (like
[prefix[$:/]]) in there!
(I'm assuming that's a typo in your previous example and should be *-*
prefix[$:/] rather than *+*.)
Thanks for the explanation As with most things Tiddly, it's opened the
door to a bunch of *new* pote
Hi Scott
Before the introduction of the ActionListops widget in v5.1.10 -- the only
option to add or remove a tag using a button were the 'tm-add-tag' and
'tm-remove-tag' messages in conjunction with an enclosing FieldMangler
widget (unless it were permissible to overwrite the 'tags' field with
H.
Any thoughts on the various advantages/disadvantages of using
<$action-listops> vs. <$fieldmangler> and <$action-sendmessage>?
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from i
On Monday, January 11, 2016 at 1:57:49 PM UTC-5, Eric Shulman wrote:
>
> Just FYI, I tried using <$action-sendmessage> with tm-add-tag and
>> tm-remove-tag, to no avail. Clearly I'm misunderstanding/misusing that
>> widget ...
>>
>
> Wrap your button inside a <$fieldmangler> This will
>
On Monday, January 11, 2016 at 10:51:21 AM UTC-8, Scott Simmons (Secret-HQ)
wrote:
>
> Thanks, Matabele! That *does* the trick in TiddlyWiki 5.1.10, all right!
> In 5.1.9 (where I'd been playing around with this), it looks like the
> <$action-listops> macro isn't part of the core.
>
Yup. listo
On Monday, January 11, 2016 at 2:02:30 AM UTC-5, Matabele wrote:
I think something like this will do the trick:
>
> <$reveal type="match" state="!!fake" text="nope">
> <$button set="!!fake" setTo="yep" class="tc-btn-invisible">
> <$action-setfield checkedtime=<> />
> <$action-listops $tags="[[tag
Hi
I think something like this will do the trick:
<$reveal type="match" state="!!fake" text="nope">
<$button set="!!fake" setTo="yep" class="tc-btn-invisible">
<$action-setfield checkedtime=<> />
<$action-listops $tags="[[tag me tagged]]"/>
Check me!
<$reveal type="match" state="!!fake" text="y
On Sunday, January 10, 2016 at 9:36:53 PM UTC-5, Matabele wrote:
> The value in 'checkedtime' toggles as expected, however the checkbox's
> have no effect?
>
H. I could've sworn I had that working last night. (And, like a
bonehead, I've already cleared my backups and can't find the one
Hi
Using this code:
<$reveal type="match" state="!!fake" text="nope">
<$button set="!!fake" setTo="yep" class="tc-btn-invisible">
<$action-setfield checkedtime=<> />
<$checkbox tag="tag me tagged">Check me!
<$reveal type="match" state="!!fake" text="yep">
<$button set="!!fake" setTo="nope" clas
*>sniff<* *I love you guys!*
Life got in the way this week, and I didn't get a chance to read and try
this until last night — but it's a clever, elegant solution.
As it turns out, you can even use a proper <$checkbox/> macro in
conjunction with it to toggle tags:
<$reveal type="match" state="
Hi Eric,
> If you want the $button widgets to *look* like checkboxes:
>
Thanks a lot for this example for having custom events attached to what
appears to be a checkbox.
Best wishes,
Tobias.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
On Monday, January 4, 2016 at 10:44:43 AM UTC-8, Matabele wrote:
>
> Currently, action widgets can not be triggered with a checkbox widget
> (although some efforts have been made in this direction.)
>
> You may, however, use a button widget. If you wish to have visual feedback
> of the state -- u
Just as a quick addition to what Matabele said, you can also make the
button look like a checkbox like this:
<$reveal type="match" state="!!temp" text="set">
<$button set="!!temp" setTo="reset" class='tc-btn-invisible'>
<$action-setfield />
<$action-setfield />
<$reveal type="match" sta
Hi
Currently, action widgets can not be triggered with a checkbox widget
(although some efforts have been made in this direction.)
You may, however, use a button widget. If you wish to have visual feedback
of the state -- use two button widgets within two reveal widgets which
toggle one anothe
19 matches
Mail list logo
