I got most of it from tiddlywiki.com and examples in this forum.
TW technology is more like learning a human language than a programming
language -- there's a handful of rules and then a whole lot of exceptions.
It would be great to write up an all-up tutorial, but like attacking a
hydra, where do you begin?
-- Mark
On Sunday, July 1, 2018 at 5:46:08 AM UTC-7, Mohammad wrote:
>
> Hi Mark,
> That't true! The other think is the many logic you can do the same thing
> with the same results.
> By the way, is there any place to have all these explained
> When use <> for variable or <<>> or{!field} or {{!!filed}} ....
>
> Cheers
> Mohammad
>
>
>
> On Sunday, July 1, 2018 at 3:49:56 AM UTC+4:30, Mark S. wrote:
>>
>> I don't know if this will fix your problem (without actually testing) but
>> one of the things that will drive you crazy (or at least me) with TW5
>> widgets is the inconsistent attributes/parameters.
>>
>> In this case, you need to call <$macrocall> with attribute "$name", not
>> "name" . Pretty much every time you use (or I use) a widget, I have to
>> double check the syntax at tiddlywiki.com, because it's different for
>> different widgets. For instance, if you had been invoking the "<$set>
>> widget, then the attribute really would have been "name".
>>
>> HTH
>> -- Mark
>>
>> On Saturday, June 30, 2018 at 4:13:19 PM UTC-7, Dave wrote:
>>>
>>> Hi, I'm struggling getting macrocall to work to allow me to use a macro
>>> within a macro
>>>
>>> Here's what I originally wanted to do:
>>>
>>> Given this macro (<<sliderO "*" "hello there">>)
>>>
>>> \define sliderO(label,text)
>>> <$set name=this value=$(currentTiddler)$ >
>>> <$button popup="$:/state/<<this>>$label$" class="btn-invisible
>>> tw-slider">$label$</$button>
>>> <$reveal type="match" text="" default="" state="$:/state/<<this>>$label$"
>>> animate="yes">
>>>
>>> $text$
>>>
>>> </$reveal></$set>
>>> \end
>>>
>>> I wanted to call that macro with the following as the text:
>>>
>>> | ''resisted finger ext'' | <<rorlcheck resfingerext>> |
>>>
>>>
>>> So the content would be revealed with the slider mechanism. The problem
>>> is that you can't have a <<macro>> within a <<different macro>> I assume
>>> because of the "<<>>" repetition
>>>
>>> ----
>>>
>>> The answer I presume from googling here is to use a macrocall, but for
>>> the life of me I can't seem to get it to work
>>>
>>> I tried setting the content as both a macro and a variable:
>>>
>>>
>>> \define motor2ndorder()
>>> | ''resisted finger ext'' | <<rorlcheck resfingerext>> |
>>>
>>> \end
>>>
>>> <$macrocall name=sliderO label="Motor 2nd Order" text=<<motor2ndorder
>>> >>/>
>>>
>>> and
>>>
>>> <$vars text="""
>>> | ''resisted finger ext'' | <<rorlcheck resfingerext>> |
>>> """></$vars>
>>>
>>> <$macrocall name=sliderO label="Motor 2nd Order" text=<<text>>/>
>>>
>>> but neither of those is working :(
>>>
>>> any suggestions?
>>>
>>
--
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/bc1f0a49-66ce-46f3-b542-d1bcf9d13379%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
