Blame MD or Android

[FrameXX]

I was actually using local variables

Oh man. In this case I described it doesn't matter if the variable is local to the macro or not. Can you send your macro?

The solution to stack everything in arrays should be also valid, bit can be harder to manage and what @Dm114 created will just ignore the notification if the macro is already execution.

 

[OscariBot]

Oh man. In this case I described it doesn't matter if the variable is local to the macro or not. Can you send your macro?

The solution to stack everything in arrays should be also valid, bit can be harder to manage and what @Dm114 created will just ignore the notification if the macro is already execution.

Exactly my point. @Dm114 macro actually ignored notification that arrived when the macro is already running....

My macro is too complicated to understand but I will try to extract just this area and upload so we can digest it together.

 

[Dm114]

Exactly my point. @Dm114 macro actually ignored notification that arrived when the macro is already running....

Sorry @OscariBot and @FrameXX but either I didn't understand your needs or you modified the mechanism of the sample I've sent but it works fine for me: be careful not to modify, nor add/delete any action outside the Iterating loop, nor modify the time MacroRunning boolean variable is updated. This is the key of the mechanism...

I just tried again with 10 notifications arriving at the same time (less than 5 seconds) and the macro ran the Iterating loop 10 times to run actions inside it.

Have you corrected my initial error where MacroRunning was set to False at the wrong place (last bottom line instead of the line before the EndIf statement)? This is one of the keys...

 

[Dm114]

Have you unchecked "Prevent multiple triggers"?

 

[OscariBot]

Have you unchecked "Prevent multiple triggers"?

I told you earlier am not using the regular MD notification trigger...
Am using notification listener plugin

 

[OscariBot]

But what the heck is the function of RAM? I thought it's suppose to store and queue unprocessed data.
In this case unprocessed notification data should be store and retrieve sequencially...

But why is it not happening that way

 

[Dm114]

I told you earlier am not using the regular MD notification trigger...
Am using notification listener plugin

Sorry I missed you were using a plugin instead of regular Notification trigger. As I don't use this plugin I'm afraid I won't be able to help further.

 

[Dm114]

But what the heck is the function of RAM? I thought it's suppose to store and queue unprocessed data.
In this case unprocessed notification data should be store and retrieve sequencially...

But why is it not happening that way

Data is always processed by apps, not by RAM. If an app doesn't process data as expected it's generally an unsolvable problem...

Good luck!

 

[OscariBot]

Sorry I missed you were using a plugin instead of regular Notification trigger. As I don't use this plugin I'm afraid I won't be able to help further.

Well @Dm114 thanks so much for your contribution so far...

Am gona still experimenting until I figure it out.

 

[OscariBot]

Data is always processed by apps, not by RAM. If an app doesn't process data as expected it's generally an unsolvable problem...

Good luck!

I really use to think every app including native android stores unprocessed data in the ram for execution....

I time I revisit my book

 

[Dm114]

I really use to think every app including native android stores unprocessed data in the ram for execution....

I time I revisit my book

It all depends on Devs...

 

[OscariBot]

It all depends on Devs...

I don't think dev can break android rules... If android OS says all unprocessed data must queue in the ram (which I honestly thought it to be) then there's nothing a dev can do other than to follow this already set rules

 

[OscariBot]

Sorry am replying this now because I was away

Thanks @FrameXX ... Your method actually worked for me ..

Special thanks to @Dm114 for your prompt suggestions even though it didn't work for me.

Like @FrameXX suggested it actually ignore other incoming notification when the macro is running.