Thanks, this is what it ended up being;
\define Tags() [[$(currentTiddler)$]] [[(EXTRA-TAG)]]
<$button>
<$action-sendmessage $message="tm-new-tiddler"
title="TIDDLER-NAME"
text="TEXT-FIELD-HERE"
tags=<>
field="FIELD-TEXT"
field2="FIELD-TEXT"
/>
''BUTTON-NAME''
Op donderdag 17 december 2
FYI:
In a button you do not need to use messages or params in the button but can
use actions= <> to drive the actions. you can also place
actionwidgets inside the button, even wrapping them in lists or
conditionally. Use the actionSend message widget etc... Then rather than
paramObject param e
Looking at the code for the Button widget, I don't see any place where
paramObject gets populated. I do see it for the send-message widget. So
I'm guessing that you can't use "paramObject" with the button widget
without hacking the button widget code.
On Wednesday, December 16, 2020 at 7:52:34
On Wednesday, December 16, 2020 at 11:00:16 AM UTC-4 Mark S. wrote:
> On Tuesday, December 15, 2020 at 8:10:42 PM UTC-8 wrote:
>
>> I often struggle with filter syntax so thanks for the counter-example as
>> I find those easiest to learn from.
>>
>> In playing around with it, there is an interes
On Tuesday, December 15, 2020 at 8:10:42 PM UTC-8 wrote:
> I often struggle with filter syntax so thanks for the counter-example as I
> find those easiest to learn from.
>
> In playing around with it, there is an interesting subtlety with Mark's
> solution that makes it slightly different/bet
I can explain what I *think* is happening. In reality, I just keep pounding
until something works.
When assigning directly via *= *the {{{ code }}} returns a *string*
formatted to look like a title list. Unfortunately, different runs inside
are separated by a carriage return. The = assignment t
A tangent. I was just looking for a more concise/intuitive/automatic way to
convert a title (or string in general) with spaces into a single title in a
title list rather than each word being separate.
I get caught up by manipulating/building Title Lists to use as tags
frequently. I guess the of
> Also, I was trying every operator to see if there was an alternative
> solution to manually wrapping the title with [[ and ]] using
> addprefix/suffix but there doesn't seem to be a replacement for the
> $vars/addprefix/addsuffix construction.
>
>
I am curious, what purpose is that serving
I often struggle with filter syntax so thanks for the counter-example as I
find those easiest to learn from.
In playing around with it, there is an interesting subtlety with Mark's
solution that makes it slightly different/better.
If the template does not already exist:
1) it will not tag the n
Yet another approach:
<$button >New Task
<$vars left=" [[" right="]]" space=" ">
<$action-sendmessage $message="tm-new-tiddler" $param="TaskTemplate"
tags={{{
[[TaskTemplate]get[tags]addsuffixaddsuffixaddsuffix]
}}} />
Mostly this demonstrates that when you use the <$action-sendmessage>
The *action-createtiddler* widget is similar but allows you to save the
name of the created tiddler somewhere for subsequent actions.
The issue that I often have is that "subsequent" does not just mean further
down the macro since actions can trigger in unpredictable ways. In this
case, if you
11 matches
Mail list logo