Follow-up question: I'd like to limit the scope of certain keyboard shortcuts to certain tiddlers only. Am I correct in saying that this would come down to encapsulating a keyboard shortcut definition within a list filter, like for instance [is[current]title[something]] would make the keyboard definition only available within a tiddler titles 'something'?
Thanks. On Tuesday, 12 February 2019 12:20:08 UTC, Hubert wrote: > > Thank you! That solves it :) > > On Tuesday, 12 February 2019 12:04:39 UTC, BurningTreeC wrote: >> >> Hi Hubert, >>> >>> the Keyboard Shortcuts >>> <https://tiddlywiki.com/#How%20to%20create%20keyboard%20shortcuts> >>> documentation >>> at tiddlywiki.com contains some information about this at the very >>> bottom of the tiddler >>> it's probably just missing an example to be clear enough, I think I'll >>> add one ... >>> >>> Here's how you do it: >>> >>> <$navigator story="$:/StoryList" history="$:/HistoryList"> >>> >>> >>> put your shortcut actions here >>> >>> >>> </$navigator> >>> >>> >>> it's necessary to wrap certain actions in Keyboard-Shortcut-Tiddlers >>> within a navigator widget. Such a widget exists for tiddlers in the story >>> river or sidebar through the $:/core/ui/PageTemplate tiddler, that >>> transcludes all other PageTemplate tiddlers. but you can imagine >>> Keyboard-Shortcut-Tiddlers being outside of the scope of that navigator >>> widget, so we need to explicitely tell it the storylist and historylist it >>> should use for navigation - then it works >>> >>> note that if your storylist and historylist are not the standard lists, >>> you'd use those tiddlers for the "story" and "history" attributes, but I >>> guess that in 95% of the cases the standard ones will do the job >>> >>> all the best, >>> btc >>> >> >> >> I forgot mentioning that for navigation using the action-navigate widget >> or the tm-navigate message I use navigator widget with more attributes, >> exactly how the $:/core/ui/PageTemplate tiddler does it, so that navigation >> also behaves the same way as clicking a navigation button or link within >> the story-river or sidebar: >> >> <$navigator story="$:/StoryList" history="$:/HistoryList" >> openLinkFromInsideRiver={{$:/config/Navigation/openLinkFromInsideRiver}} >> openLinkFromOutsideRiver={{$:/config/Navigation/openLinkFromOutsideRiver}} >> relinkOnRename={{$:/config/RelinkOnRename}}> >> >> >> >> >> -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/4adf08fe-89aa-43a7-a58a-d7334aa126b4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
