So now that 5.1.23, I can post the example I've been working on:
https://marxsal.github.io/various/playground.html#Excise%20from%20View%20Template%20Example
If you look at the code, you'll see that I have to use a tiddler that's
made in advance of the drag/drop routine. The tiddler that's made
I'm not using a button. I'm using droppable. So all actions are happening
inside an action macro.
The button example was only an example, and I'm afraid has confused the
issue. Ignore what happens with buttons.
On Saturday, December 19, 2020 at 1:55:40 AM UTC-8 PMario wrote:
> @Mark Use button
@PMario
I guess the quirk is with <$fieldmangler> ... I think in particular if it
has a transcluded tiddler=. It executes first ... even when everything is
put into actions= as you suggest. But several workarounds were identified
that either:
1) avoid using the add-tag message (and
@Mark Use button actions like this,
\define actions()
ALL action widgets come here
\end
<$button actions=<> >click
Otherwise you beg for trouble.
-mario
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop
Try this:
<$button>
<$action-setfield $tiddler="$:/savedtitle" text="" />
<$action-createtiddler $basetitle="Secret" $savetitle="$:/savedtitle"
tags="Excerpt" text="do you see me now 2?" />
<$action-setfield $tiddler="testtiddler" text={{$:/savedtitle}} />
*<$fieldmangler
BTW, what I'm working on is a tool that will let you select your text in
the view template, drag and drop it to the drop zone in the sidebar, and
automatically insert a link or transclusion into the place in the
viewtemplate where the original text occurred. In other words, it works
like
Ok, I think I'm back to "doesn't work with dropping." Might have to revisit
tomorrow.
Thanks!
On Friday, December 18, 2020 at 8:28:47 PM UTC-8 TW Tones wrote:
> Well here is my test on the pre-release.
>
> <$button>
> <$action-setfield $tiddler="$:/savedtitle" text="" />
>
Well here is my test on the pre-release.
<$button>
<$action-setfield $tiddler="$:/savedtitle" text="" />
<$action-createtiddler $basetitle="Secret" $savetitle="$:/savedtitle"
tags="Excerpt" text="do you see me now 2?" />
<$action-setfield $tiddler="testtiddler" text={{$:/savedtitle}} />
Ok, the navigation actually occurs AFTER the entire routine has finished.
Inside the routine, the value of the saved tiddler is unavailable.
To see this, try this variation:
<$button>
<$action-createtiddler $basetitle="Secret" $savetitle="$:/savedtitle"
tags="Excerpt" text="do you see me now
Mark,
Maybe with drop action, but as you can see action navigate is only using a
transclusion, I can even use {{$:/savedtitle}} in the button title or
after.
With a qualified save title the last title can be stored indefinitely as
well, so I find it hard to imagine.
What were you trying to
Perhaps action-navigate works differently than action-setfield, or perhaps
everything works differently with a drop action.
On Friday, December 18, 2020 at 6:24:11 PM UTC-8 TW Tones wrote:
> Folks,
>
> I may be missing something here, or perhaps 5.1.23 has reverted (untested
> by me yet), but
Folks,
I may be missing something here, or perhaps 5.1.23 has reverted (untested
by me yet), but I cant help but feel these posts are miss-representing
things somehow.
The drop actions do add complexity to this but inside a single button I
have used createtiddler then referenced the save
The problem is highlighted by something like this:
\define dropaction()
<$action-createtiddler $basetitle=<> />
<$list
filter="[all[tiddlers]search:titlesort[created]last[]]"
variable="lastcreated">
<$fieldmangler tiddler=<>>
<$action-sendmessage $message="tm-add-tag" $param=<>/>
\end
On Thursday, December 17, 2020 at 7:33:30 PM UTC-8 TW Tones wrote:
>
>
> Otherwise; *accept or generate the new tiddler name before
> $action-createtiddler *
>
>
This somewhat obviates the utility of the $savetitle attribute, since the
results are not available until the containing
<$action-createtiddler allows you to created tiddlers "silently", you then
use as Mario said tm-navigate or even edit tiddler ( tm-edit-tiddler ) ,
when you can rename it.
Before opening it to edit where you could rename it, the $savetitle remains
valid and you could use it to perform other
That's an interesting idea. But tm-link-to doesn't show up anywhere in the
documentation, or a search in system or shadows. Are you sure it exists yet?
Thanks!
On Thursday, December 17, 2020 at 6:12:12 PM UTC-8 PMario wrote:
> Hi Mark,
> You may be able to use the <$linkcatcher widget to
On Friday, December 18, 2020 at 3:12:12 AM UTC+1 PMario wrote:
So your first action define the $savetitle ... and a second actions sends
> a tm-link-to, which is catched by the linkcatcher actions. It should / may
> be available.
>
I meant tm-navigate ...
-m
--
You received this message
Hi Mark,
You may be able to use the <$linkcatcher widget to trigger a new action. ...
So your first action define the $savetitle ... and a second actions sends
a tm-link-to, which is catched by the linkcatcher actions. It should / may
be available.
With 5.1.23 there is a new
In this case there is no button -- it's being triggered by a drop event
onto a droppable widget.
Thanks!
On Thursday, December 17, 2020 at 5:22:40 PM UTC-8 Eric Shulman wrote:
> On Thursday, December 17, 2020 at 4:07:38 PM UTC-8 Mark S. wrote:
>
>> In prerelease 5.23, if I run something like:
On Thursday, December 17, 2020 at 4:07:38 PM UTC-8 Mark S. wrote:
> In prerelease 5.23, if I run something like:
> <$action-createtiddler $basetitle="Excerpt" $savetitle="$:/savedtitle"
> tags="Excerpt" text=<> />
> The title saved in $:/savetitle doesn't become available until AFTER the
>
20 matches
Mail list logo
