This is related to the post regarding usage of parameter widget in procedures . Here I am testing usage of parameter widget in procedures. Here is the code. \procedure dyn-table-test() <$parameters op-1="""<% if [{!!op-1-value}is[blank]] %> <<op-1>> <% elseif [<currentTiddler>!has[op-1-value]] …

I think your problem is that, as @Springer pointed out, op-1={{{ [<currentTiddler>get[op-1-value]] ~[<op-1>] }}} creates a loop where <<op-1>> falls back to looking at itself rather than using the parameter you supplied in the macrocall. I believe this produces your intended behavior: \procedure d…

[image] arunnbabu81: op-1="""<% if [{!!op-1-value}is[blank]] %> <<op-1>> I’m not following everything, but you seem to have a self-referring loop here. It looks like you’re effectively making a circular reference here — specifying that the op-1 variable (parameter) should equal itself if op-…

[image] What can be accomplished with procedures that is not possible or difficult to do with macros? Tips & Tricks Very cool! I expect to use these quite a bit. With your help, I understand that I can design a repeatable pattern (procedure) whose various param…

[image] arunnbabu81: I saw you have used version=<<version>> Ah, that worked only because <<version>> is already a defined macro, if I recall the context.

[image] Springer: I think you wanted to specify {{!!op-1}} as field value, not as variable value <<op-1>>, in your parameters declaration. There is a field called op-1-value . No op-1 field exist. What i was trying is use the op-1-value if it is present in the tiddler, otherwise use the para…

[image] op-1 is a parameter I am defining using parameter widget. op-1-value is the field present in the tiddler

[image] arunnbabu81: What i was trying is use the op-1-value if it is present in the tiddler, otherwise use the parameter value i have specified in the procedure call. So: <$parameters param-1={{!!param-1-value}} op-1="""<% if [<currentTiddler>!has[op-1-value]] %> <<param-1>> <% else %> …

[image] arunnbabu81: What i was trying is use the op-1-value if it is present in the tiddler, otherwise use the parameter value i have specified in the procedure call. Usually you can specify the parameter value in the procedure call, and the parameters widgets give you a fall-back. Do you m…

[image] Springer: Do you mean that you want the parameter to refuse to be overwritten by what you specify, in the event that the field value is present? Yet you do want to be able to call the procedure with parameters, even when these should be overridden (because the tiddler’s field value shoul…

[image] Springer: If so, I think you need a third parameter, one that you will not be tempted to specify manually in the procedure call. That third parameter will look for [has[op-1-value]], retain that value if it’s available, and only then consider your op-1 as specified in the procedure call. …

My first thought is that you generally want to use a filtered transclusion to define a parameter; anything in quotes will be treated as a literal string and not wikified before substitution (which I assume you want to happen). And you probably don’t need the <% if %> construction, since you can achi…

Help need to define a conditional parameter for a procedure

arunnbabu81 July 30, 2024, 6:16pm 3

I was trying to use this code you shared previously.
There I saw you have used version=<<version>>
I was trying to make that into a conditional parameter