Thanks for all the input! I thought about this a little more. The reason for putting the parameter into a field is so that a user can change it.
It is quite possible the macro will be used in many places, so using the $list widget's *search* or *contains* operator suggested by Eric & Mark , both interesting solutions that had not occurred to me, might not be a viable idea. Tony's suggestion to provide for the creation of a settings system tiddler meant making a button, which was fine, as a change of the setting anyway needs user input. And since there is a default *separator* parameter, this would work well. However this led me to another idea, which was to have an *$edit-box* in the macro tiddler to change the *separator* field. Since the change would be only ONE character typed, the loss of focus on the edit box will be an acceptable compromise. Now I'm starting to figure out how to limit the input into the edit box to just *1* character. This does not limit the input: Change the present ''separator'' here: <$edit-text field="separator" placeholder="" size="1"/><small> ( Default is `-` )</small><br> <small>When you delete the present separator, you may have to click again in the box before you can type the new one.</small> Though the HTML <input> tag has an attribute: *maxlength* : it is not an attribute of the *$edit-text* widget as Mark pointed out in the Post last year: Question about maxlength <https://groups.google.com/forum/#!topic/tiddlywiki/Ch8NL6-mG9w/discussion> It may be useful for TiddlyWiki to include *maxlength* as an attribute of the *$edit-text* widget. Perhaps the safe way is to use just the FIRST character in the separator field. If I ever finish the macro successfully, I may include it on Mohammad's : Yazd: a KISS collection of Tiddlywiki macro <https://groups.google.com/forum/?hl=en#!topic/tiddlywiki/1btgb6dmiBU> :though he may reject it as it is turning out to be a MICK macro (MICK - Made it Complicated, Knucklehead) Cheers! On Saturday, March 23, 2019 at 7:17:16 AM UTC+7, TonyM wrote: > > S s > > Nessesity is the mother of invention, but sometimes you can avoid a > particular nessesity. Perhaps Let them rename the macro but let the macro > create a settings tiddler, a system tiddler that stores settings that they > do not care about and will not rename. Create the settings tiddler if it > does not exist but use its values if it does. > > Never the less if a special variable was available to access the title of > the tiddler in which the macro resided rather than the current tiddler it > would be useful. That would need a tiddlywiki DOM expert to implement. > > It would be useful > For your use case > For tiddler s generated from templates that contain macros that inherit > the macronames from the tiddler name. (eg new field definition tiddlers > creating fieldname macros) > some tricky self referential algorithiums. > > Regards > Tony > > -- 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/ad26cea3-80e6-4e01-b044-427ea01bec85%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
