Changes for the "Test macro" option

[Golem64]

Hello, i would like to ask if you could change the way testing the macro works.
Currently, when executing with that, it uses the last trigger that have been triggered to call the macro.
I think it would be a better idea to launch the macro without any trigger, Wich would fix a lot of bugs in some cases.
I personally would like to use it for other intentions such as "when the macro is executed without any trigger, show this menu".
For me, testing the macro is another way to do some action separately of others triggers. If we want to launch from the last trigger, we can do it manually from inside the macro.
Thanks

 

[Snurre]

Is it not the same as "Test Actions" instead of "Test Macro"?

 

[Abalsam]

Test action literally tests the selected line. It sounds like he is asking for a method to test the entire macro but if no specific trigger invoked the macro.

To my mind, a better option (which I believe is available now) is to test each trigger in the macro (to make sure they all work as expected). To test how the macro would run if it is not launched from a trigger, use an empty trigger without testing for it in actions.

I hope that helps.

 

[Snurre]

Test action literally tests the selected line.

That is not what I wrote
It's"Test actions" under three dots menu, which tests the whole macro

 

[Abalsam]

That is not what I wrote
It's"Test actions" under three dots menu, which tests the whole macro

OH. Sorry I misunderstood.

 

[Pseudocyclic]

Currently, when executing with that, it uses the last trigger that have been triggered to call the macro.

Are you sure?

 

[Golem64]

Are you sure?

Yes, I'm 100% sure. I talk about long pressing the macro in the macro list to click on "Test macro"

 

[Pseudocyclic]

Yes, I'm 100% sure. I talk about long pressing the macro in the macro list to click on "Test macro"

How do you know that the last trigger that fired is fired again?

 

[Golem64]

How do you know that the last trigger that fired is fired again?

Because I made some tests. Try and make a macro with two triggers that make something different. Execute the first trigger manually, then try with "test macro". The same action sould fire. Now do that but with the second trigger, and it will do the actions of the second trigger.

 

[Pseudocyclic]

Because I made some tests. Try and make a macro with two triggers that make something different. Execute the first trigger manually, then try with "test macro". The same action sould fire. Now do that but with the second trigger, and it will do the actions of the second trigger.

I think it works differently - I think the macro keeps track of which trigger fired last, and when you ask 'which trigger fired?' it's treated as if the question was 'which trigger fired last?'.

 

[Snurre]

Because I made some tests. Try and make a macro with two triggers that make something different. Execute the first trigger manually, then try with "test macro". The same action sould fire. Now do that but with the second trigger, and it will do the actions of the second trigger.

That is Not correct !
I don't know what it is you are trying to test ?
Try the following macro and it will show nothing when you try to run test macro/actions
And of course it shouldn't, there is no trigger fired before you actually press one of the buttons

 

[Golem64]

That is Not correct !
I don't know what it is you are trying to test ?
Try the following macro and it will show nothing when you try to run test macro/actions
And of course it shouldn't, there is no trigger fired before you actually press one of the buttons
View attachment 2412

Yes, but as soon as you fire a trigger, it's going to start fire the last trigger again if you use the macro testing

 

[Snurre]

Not here