> > > The link catcher only responds to navigation messages. It absorbs the > navigation event and just sends the message identified in the `message` > attribute. So, one could create a chain of navigation message handlers, I > think, but not of arbitrary messages. > > So it stops the event propagation right? Maybe it could be interesting to capture a event, react and raise a secondary event.
> > I noticed the linkcatcher has a special feature that is not used in any > place > > The linkcatcher's ability to forward a message is actually used as part of > the tag drop down handling: > > > https://github.com/Jermolene/TiddlyWiki5/blob/master/core/ui/EditTemplate/tags.tid#L28 > > Thank you > > Other question: Is possible to use a tw-save-tiddler without navigating > to it? I'm editing some drafts from other tiddlers and I don't want to open > the resultant tiddlers after clicking my custom save button. > > It sounds like you might be better off displaying these tiddlers in a > custom sub-story. See the interactive version of this tiddler on > tiddlywiki.com: > > http://tiddlywiki.com/static/Creating%2520SubStories.html > > If you put the tiddlers you're editing in a story you'll still get the > navigation behaviour, but the navigation will take place within the > substory, which is probably what you want. > > Best wishes > > Jeremy > That is very interesting. Is not what I was looking for exactly but it could work. But I see it very interesting for TOC tables. Really really interesting. -- 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 post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
