PSA: When working inside some FUNCTIONS, you must use the % notation to reference variables, not just the variable name itself

[peternlewis]

@JuanWayri

In this particular case, they sent me screenshots of both the documentation and their macros, which made it clear that this issue was worth highlighting.

I can see what they/you are saying.

Basically that the Set Variable to Calculation action very explicitly says to note use token processing in the calculation field, and yet if you use those couple functions you actually do have to use token processing, within the parameters of those functions.

That's a valid comment, but it's a little problematic to address, because for the most part that advice against using tokens is exceptionally good and important and I'm hesitant to water it down even to allow for those functions.

In reality, those functions are fairly esoteric, and the documentation on those functions is quite explicit and immediately indicates the need for tokens to reference things.

At some point it is a balancing act in terms of what to provide where. To add more information about those specific functions in the Set Variable to Calculation action would, I think in this case, likely result in more confusion than it solves.

[JuanWayri]

@peternlewis

At some point it is a balancing act in terms of what to provide where. To add more information about those specific functions in the Set Variable to Calculation action would, I think in this case, likely result in more confusion than it solves.

I don’t think there’s any need to change how the calculations work or modify the existing documentation on calculations. However, I do believe that adding an extra example or a screenshot to the wiki pages for the LINES, CHARACTERS, and WORDS functions could be helpful. It would give newcomers a clearer understanding when they try to use those functions without introducing any confusion elsewhere.

[Nige_S]

@peternlewis

Not really, more accurately it goes:

calculation input is `CALCULATE(Local_c)`
text process of `Local_c` is `Local_c`
calculation input of `Local_c` results in calculation of `Local_c`’s value
`Local_c` contains text `Local_b+1` so calculation of that is 1 more than the value of `Local_b`
`Local_b` contains text `Local_a+1` so calculation of that is 1 more than the value of `Local_a`
`Local_a` contains text `1` so calculation of that is 1.

Thank you for that correction, @peternlewis -- and thank you (again!) for your time. As always, you've gone above and beyond...

@JuanWayri

However, I do believe that adding an extra example or a screenshot to the wiki pages for the LINES, CHARACTERS, and WORDS functions could be helpful.

Yes, one that uses the %Variable% text token would make it more explicit. Not everyone will see the %CurrentClipboard% text token and realise that means "you should use a text token from the list linked above".

But I see that, yet again, Peter is a step ahead...

[peternlewis]

@JuanWayri

However, I do believe that adding an extra example or a screenshot to the wiki pages for the LINES, CHARACTERS, and WORDS functions could be helpful. It would give newcomers a clearer understanding when they try to use those functions without introducing any confusion elsewhere.

I've added %Variable% examples for the LINES , CHARACTERS , and WORDS functions.