If the $ is needed in some cases, is there an argument for allowing it for all widget parameters to improve consistency?
As an example of the result of the confusion caused by inconsistency, a couple of times I have neglected the $ in the $tiddler and $field parameters of a $action-setfield widget, with the result that, when activated, the action defaulted to the text field of the current tiddler, overwriting all the text I was working on! That's extremely annoying, and quite difficult to debug when you no longer have the wikitext that caused the problem! Neil. On Saturday, 7 March 2015 16:54:47 UTC, Eric Shulman wrote: > > On Saturday, March 7, 2015 at 8:00:53 AM UTC-8, Jed Carty wrote: >> >> Action widgets use $ for the parameters, I am assuming that is because >>> you can pass (some of) them lists of name=value pairs, like the setfield >>> widget. The $ in needed to distinguish between things like in this example >>> >> >> <$action-setfield $tiddler=SomeTiddler tiddler=hi/> >>> >> >> which sets the field called tiddler of SomeTiddler to hi. I am assuming >> that $ was picked because it isn't a valid symbol in a field name. >> > > > The $ prefix is used to differentiate parameters used by the widget itself > as compared to parameters without the $, which are simply "passed through" > to the specific macro or action being invoked by the widget. For most > widgets (except $macrocall and $action-xxx), the parameters do not have the > $ prefix. > > -e > -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
