Change the story-river & move to the top and NodeJs stubborn tiddlers

45 views
Skip to first unread message

Riz

unread,
Nov 24, 2016, 8:27:13 AM11/24/16
to TiddlyWiki
So I am trying to change the story river using action-listops and move to the top of the new story-river. Sample code I tried

<$set name=target filter="[list[$:/StoryList]first[]]">
   <$button>HelloThere
         <$action-listops $tiddler="$:/StoryList"   $filter=[tag[HelloThere]]/>
         <$action-navigate $to=<<target>>/>
   </$button>

   <$button>Learning
         <$action-listops $tiddler="$:/StoryList"   $filter=[tag[Learning]]/>
         <$action-navigate $to=<<target>>/>
   </$button>
</$set>

What it does is this - sets the story-river correctly, but weirdly the tiddler that was at the top of story-river before clicking the button is still there, as a missing tiddler (despite being very much not missing)

Same result with this

<$button>HelloThere
      <$action-listops $tiddler="$:/StoryList"   $filter=[tag[HelloThere]]/>
       <$set name=target filter="[list[$:/StoryList]first[]]"><$action-navigate $to=<<target>>/></$set>
</$button>

<$button>Learning
       <$action-listops $tiddler="$:/StoryList"   $filter=[tag[Learning]]/>
       <$set name=target filter="[list[$:/StoryList]first[]]"><$action-navigate $to=<<target>>/></$set>
</$button>

Also with <$button to=<<target>>>. Is there a way to specify that the navigate widget is execute after the listops widget? Despite being writtern after the listops, the navigate is carried out first.


As for Nodejs stubborn tiddlers, I cannot seem to be able to delete tiddlers in Nodejs. It simply keeps coming back. Unless I end the session, go to the folder and delete them using file explorer, the tiddlers refuse to be deleted. Is this an individual issue or a known one?
Reply all
Reply to author
Forward
0 new messages