I can see how the following does not work because, presumably, the a has not been “processed” when b calls/fallsback on it: \procedure test(a:"foo", b:"<<a>>") <<b>> <<test>> desired outcome: foo …but I am a bit confused why the following does not work. I had expected a to have been “processed” …

Hi @twMat the \procedure pragma only supports literal strings as the default values for parameters. You can use the underlying <$parameters> widget instead which does support dynamically computed default values.

Some helpful examples of parameter widget usage by Mohammad: [image] Parameterized Transclsuion: The Parameters Widget One interesting new feature in TiddlyWiki 5.3.0 is the ParametersWidget and Parameters pragma. I like to ask developers and supper users to s…

Hi @twMat In order to try Jeremy’s and Saq’s suggestions, don’t forget to explicitly call inner, likeso: \procedure outer(a:"foo") \procedure inner() <$parameters b=<<a>> > <<b>> \end inner <<inner>> \end outer <<outer>> expected outcome: foo

Good point. It is easy to assume that the inner procedures are being automatically called as one calls for the container.

Any way to make a procedure param use another procedure param as fallback?

saqimtiaz July 16, 2024, 4:56pm 3

Some helpful examples of parameter widget usage by Mohammad:

2 Likes