Well, I'm impressed. :-)
It's very nice of you to explain all this and I think I understand the
basic principle.
After reading the documentation - is there a special reason, that you did
use $field="tags" $subfilter="+[toggle[urgent]]" instead of
$tags="+[toggle[dringend]]"? (just to proof I
Well that fits my needs. Even if I don't have the slightest idea what you
have done. :D
That will be the next step ...
Thank You!
PMario schrieb am Montag, 31. Mai 2021 um 11:49:48 UTC+2:
> Hi,
> Try the attached template tiddler.
>
> \define toggle-urgent()
> <$action-listops
... in the ViewTemplate.
I would like to use it as a transclusion in different lists ...
PMario schrieb am Montag, 31. Mai 2021 um 11:30:57 UTC+2:
> Hi Jens,
> Is it intended to be part of the ViewTemplate or the EditTempate?
> -mario
>
>
--
You received this message because you are
Hi there,
I'm trying to toggle the tag 'urgent' via two different buttons and
switching between them via reveal:
<$fieldmangler>
<$reveal type="match" state={{!!title}} tag="urgent"><$button
class='tc-btn-invisible' message="tm-remove-tag"
param="urgent"><$reveal
type="nomatch"
Thank You!
I was somehow confused, because I'm sure it worked some time ago. Is it
possible that the alphabetical order of the tags has something to do with
this? Because there is another nested list (with different tags as
parameters) and it worked out well.
Eric Shulman schrieb am Mittwoch,
Hi,
bringing this up again ...
I want to exclude projects with tasks tagged with 'A'. Somehow it doesn't
work out as expected (well it did, something changed and I'm not sure what
and why ... :-\ )
I added !tag[A] in the second filter:
<$list filter="[tag[project]sort[]]">
<$list
Well, that solved more than one problem, :-)
Thank you!
Eric Shulman schrieb am Samstag, 22. Mai 2021 um 11:57:53 UTC+2:
> On Saturday, May 22, 2021 at 1:16:55 AM UTC-7 JM wrote:
>
>> Status: <$select field='Status' default='new'>
>> new
>> A
>> B
>> C
>> D
>>
>>
>
> The $select widget creates
Hi there,
I use a select widget to fill a certain field. I would like to see the
current field value - if set - in the dropdown-menu.
Status: <$select field='Status' default='new'>
new
A
B
C
D
So now the select widget shows 'new', even, if 'A' is set as field value.
Is it possible to show A
Yes, thank you very much!
Eric Shulman schrieb am Donnerstag, 18. Februar 2021 um 14:32:34 UTC+1:
> On Thursday, February 18, 2021 at 3:47:01 AM UTC-8 JM wrote:
>
>> Next step would be understanding what you have archieved with "limit[1]".
>> Ist the literal content of variable relevant?
>>
>
Thank you! :-)
Next step would be understanding what you have archieved with "limit[1]".
Ist the literal content of variable relevant?
Eric Shulman schrieb am Donnerstag, 18. Februar 2021 um 11:08:22 UTC+1:
> On Wednesday, February 17, 2021 at 10:35:15 PM UTC-8 JM wrote:
>
>> Something
Something changed. Using my first solution, the space between project title
was 'big', as If there was an empty list behind the project title of
projects without tasks tagged CAD. Now there is no more space between those
projects and the following project.
Perhaps my description was bad (not
Somehow, this doesn't work out. Projects without tasks tagged CAD still
appear in the list.
Eric Shulman schrieb am Mittwoch, 17. Februar 2021 um 17:10:26 UTC+1:
> Notes:
> * used *<$link />* abbreviated syntax instead of verbose *<$link
> to={{!!title}}><$view field="title"/>*
>
Thx for the
Hi there,
I use nested lists to organize my To-Do-List
<$list filter="[tag[project]sort[title]]">
<$link to={{!!title}}>''<$view field="title"/>''
<$list filter="[is[current]tagging[]tag[CAD]sort[title]]">
<$link to={{!!title}}><$view field="title"/>
Is ist possible to show only those
As I need this button quite often - is it possible to store the code of the
button in a tiddler and use it as a reference?
JM schrieb am Freitag, 12. Februar 2021 um 19:46:38 UTC+1:
> This works out well! Thank you!
>
> JM schrieb am Freitag, 12. Februar 2021 um 18:47:21 UTC+1:
>
>> Sorry, now
This works out well! Thank you!
JM schrieb am Freitag, 12. Februar 2021 um 18:47:21 UTC+1:
> Sorry, now I realized it, I'll give it a second try!
>
> JM schrieb am Freitag, 12. Februar 2021 um 18:45:34 UTC+1:
>
>> No, unfortunately that makes no difference.
>> tags={{{ [] }}}
>> will also
Sorry, now I realized it, I'll give it a second try!
JM schrieb am Freitag, 12. Februar 2021 um 18:45:34 UTC+1:
> No, unfortunately that makes no difference.
> tags={{{ [] }}}
> will also split a title consisting of multiple words into multiple tags.
>
> Mark S. schrieb am Freitag, 12. Februar
No, unfortunately that makes no difference.
tags={{{ [] }}}
will also split a title consisting of multiple words into multiple tags.
Mark S. schrieb am Freitag, 12. Februar 2021 um 18:35:56 UTC+1:
> You need to wrap the tiddler name with double braces, since the tags field
> is a list field.
Sorry, of course tags=<>
--
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...@googlegroups.com.
To view this discussion on the web visit
Hi there,
I hope the title gives an idea of my problem:
I'm working on my own To-Do-TiddlyWiki and I have build a list where the
tasks are listed by projects. That works out well. Now I want to have a
button added behind the project-title that adds a tiddler tagged with the
specific title:
WFM - Mozilla/5.0 (X11; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0,
Ubuntu 16.04 LTS, using a symlink.
Thank you!
Am Mittwoch, 15. November 2017 22:12:45 UTC+1 schrieb BJ:
>
> I am just testing a new release, it should be ready within the hour.
>
>
> On Wednesday, November 15, 2017 at
20 matches
Mail list logo
