Thank you Eric! Each time you post this I a reminded of all the other times
you post this! Thank you for being patient and persistent.
Diego
On Saturday, July 28, 2018 at 5:30:43 PM UTC-5, Eric Shulman wrote:
>
> On Saturday, July 28, 2018 at 1:28:39 PM UTC-7, Mark S. wrote:
>>
>> AFAIK state
Just a tip for all.
When you want to put a variable in a widget parameter use the macrocall widget
instead to invoke the widget then you can pass variables.
Regards
Tony
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this
On Saturday, July 28, 2018 at 1:28:39 PM UTC-7, Mark S. wrote:
>
> AFAIK state can only take a text reference. The Reveal widget acts the
> most like structures in other languages that people are familiar with, so
> it would be useful if it could make variable/variable comparisons as well.
> On
AFAIK state can only take a text reference. The Reveal widget acts the most
like structures in other languages that people are familiar with, so it
would be useful if it could make variable/variable comparisons as well.
-- Mark
On Saturday, July 28, 2018 at 1:00:58 PM UTC-7, Diego Mesa wrote:
Hey Mark,
Thanks for this! Just to confirm, state *can't* take a variable directly
right? Like:
<$reveal state=<> type="nomatch" text="0"
<>
I tried it but it didnt work for me so Im just making sure Im not doing
anything silly.
On Saturday, July 28, 2018 at 1:03:02 PM UTC-5, Mark S.
Thanks Mark. This worked like a charm:
<$list filter="[tagcount[]] -[[0]]" variable=result>
<>
On Saturday, July 28, 2018 at 12:17:18 PM UTC-5, Mark S. wrote:
>
> A filter ending in count[] will never be empty because zero is a number!
> But (at least in my test) you can subtract out the 0:
>
That could work too, though it would involve making an extra tiddler to put
the comparison zero and more widgets:
<$list filter="[has[yourfilter]count[]]" variable=result >
<$reveal state="zerostate" type="match" text=<>>
NOTHING HERE FOLKS!
<$reveal state="zerostate" type="nomatch" text=<>>
<>
Hey mark,
Good idea. Why doesnt using a reveal and comparing against "0" work?
Diego
On Saturday, July 28, 2018 at 12:17:18 PM UTC-5, Mark S. wrote:
>
> A filter ending in count[] will never be empty because zero is a number!
> But (at least in my test) you can subtract out the 0:
>
> <$list
A filter ending in count[] will never be empty because zero is a number!
But (at least in my test) you can subtract out the 0:
<$list filter="[tagcount[]] -[[0]]" variable=result
emptyMessage="none">
Then it will return "none" for the zero count.
-- Mark
On Saturday, July 28, 2018 at 9:18:29
When I use
<$list filter="[tagcount[]]" variable=result
emptyMessage="none">
<>
I still get zeroes as the return. I added the empty message and it doesn't
show up, returns 0 instead.
On Wednesday, July 25, 2018 at 6:56:31 PM UTC-5, TonyM wrote:
>
> Joe,
>
> Try using count as a filter
Joe,
Try using count as a filter operator on a list
<$list filter="[yourfilter]count[]" variable=result>
<>
In the above case result will display the count, but nothing will show if
nothing or 0 items are in the result.
And you could extend this with the emptyMessage (not what you are asking
11 matches
Mail list logo
