Can a macro determine if its Conflict Palette was clicked?

[_jims]

When a Conflict Palette (CP) appears, the macros on the palette can be triggered from that CP in at least two ways:

1. by clicking the macro name on the CP, or
2. by typing letters until a macro is uniquely identified.

Am I missing any other ways?

My question is: can the macro that is triggered determine which method was used to launch it? (I'd like to vary the macro behavior depending on the method.)

Unfortunately, the following tokens are always the same with one exception*:

• %TriggerValue% : [ null ]*
• %TriggerBase% : Palette
• %Trigger% : Duplicate Macro Palette

*unless a modifier is down when using the clicking method

Surely I'm missing something because I can only think of one very cumbersome method: use an If action and check The key A is down, The key B is down, The key C is down...

Any better ideas? Thanks in advance.

[DanThomas]

I really can't think of any way to do this, although I don't make use of conflict palettes, so my knowledge is limited (or non-existent) in this area.

You might want to rethink your approach. Maybe there's another way to obtain your ultimate goal.

That's all I got.

[martin]

@_jims

Surely I'm missing something because I can only think of one very cumbersome method: use an If action and check The key A is down, The key B is down, The key C is down...

Perhaps use "If mouse button down" instead?

[_jims]

@martin

Perhaps use "If mouse button down" instead?

@martin, thanks for the suggestion—that was my first thought too. But a Conflict Palette does not dismiss until the mouse button is released.

I have verified that The Key x is down works, however each If condition is a single hard-coded key. In my use case I'll have many similar macros with a wide variety of names. I was hoping to have constant group of actions that I could copy into each one.

[_jims]

@DanThomas

You might want to rethink your approach. Maybe there's another way to obtain your ultimate goal.

That's all I got.

Okay, thanks for weighing in.

[martin]

@_jims

But a Conflict Palette does not dismiss until the mouse button is released.

That's very unfortunate.

Another way I can think of is to make a subroutine macro, put all the keys you may press as condition, return T/F depending on whether any of the keys are down. If none of the keys are down, then the macro is triggered by mouse click.

[_jims]

@Martin, thanks again for the comment.

@martin

That's very unfortunate.

Well, when you think about it, mouse up is the way UI elements normally work. As a user, you get a final chance to change your mind (i.e., you click, see the item that is selected, don't like it, move your mouse to deselect to essentially cancel your choice.)

@martin

Another way I can think of is to make a subroutine macro, put all the keys you may press as condition, return T/F depending on whether any of the keys are down. If none of the keys are down, then the macro is triggered by mouse click.

I did test an If action with all of the letters, numbers, and special characters—it's remarkably fast. So, even though it was a bit tedious to create, it works well.