Convert A Macro To A Subroutine Needs Finder Selection

[Joel]

@Nige_S

@Joel

I am mely interested in your comments and thoughts, including what else should be changed or fixed.

If it's all working properly then we're probably down to optimisations and style choices now. For example, this:

...is an unnecessary case-switch because the text-matching test is case-insensitive

Appreciated.

I learnt something new. It is gone!

@Nige_S

...you've a mix of double- and single-underscore variables:

...and so on.

Appreciated.

I will check but it is my understanding that one uses double underscores for variables that appear in Prompt For Input actions so that the "Local" does not appear. I will re-read the WiKi to make sure this is correct and adjust accordingly.

@Nige_S

But there comes a point when you should cry "Enough!" and get on with using the damn thing

Agreed, I feel I am there! No doubt! Really just trying to learn the finer points.

@Nige_S

...tell me more about the challenge to trigger this by URL!!

The URL Trigger is documented on the Wiki. But the "challenge" is more a demo of the advantages of separating out the Trigger and parameter processing from the main body of the macro -- it makes it easy to drop in another Trigger, another parameter format, with its own processing routine to produce the needed inputs for the main body.

The URL Trigger is a good demo of that because you are going to have to URL encode your parameter (or make it similarly "web safe") before sending, so your macro will need to a) determine that a URL Trigger was used and b) decode then process the parameter to your start variables.

But more a fun exercise than anything else!

I accept the challenge which I understand to be to trigger the macro via the URL trigger.

Stay tuned!

[Nige_S]

@Joel

I will check but it is my understanding that one uses double underscores for variables that appear in Prompt For Input actions so that the "Local" does not appear.

That used to be the case, but KM's got a lot smarter in parsing out scope and name for "Prompt for User Input":

So pick whichever you like but stay with that format wherever possible because:

1. You've enough to think about without remembering whether to use none, one, or two underscores in a particular Variable name
2. Staying consistent lets you automate things easily. Here's my "variables" text expansion:

KM Variable.kmmacros (5.7 KB)

Image

[Joel]

@Nige_S

@Joel

I will check but it is my understanding that one uses double underscores for variables that appear in Prompt For Input actions so that the "Local" does not appear.

That used to be the case, but KM's got a lot smarter in parsing out scope and name for "Prompt for User Input":

So pick whichever you like but stay with that format wherever possible because:

1. You've enough to think about without remembering whether to use none, one, or two underscores in a particular Variable name

Ahhh, the WiKi must not have been updated because U certainly did not di that without reading it somewhere.

Question -- and I know I can test this -- but I am super curious and need to jump on a Teams call, does one still need the "__" when using Prompt With List to separate what is displayed in the dropdown box and what is acted upon?

@Nige_S

2. Staying consistent lets you automate things easily. Here's my "variables" text expansion:

KM Variable.kmmacros (5.7 KB)

Image

Super cool, smart and foolproof!

[Nige_S]

@Joel

Question -- and I know I can test this -- but I am super curious and need to jump on a Teams call, does one still need the "__" when using Prompt With List to separate what is displayed in the dropdown box and what is acted upon?

Yes.

Stripping scope labels for a "pretty Prompt" only has to worry about a limited set of reserved words -- "Global", "Instance", and so on -- whereas the number of values possible in a value__friendlyLabel formatted is list is pretty much infinite so a defined structure is required.

[Joel]

@Nige_S

Stripping scope labels for a "pretty Prompt" only has to worry about a limited set of reserved words -- "Global", "Instance", and so on whereas the number of values possible in a value__friendlyLabel formatted is list is pretty much infinite so a defined structure is required.

Ahh, makes perfect sense!

Thank you.