Hmm, i do not know about triggername.
Many thanks, I'll look into it.
Search found 69 matches
- 07 Mar 2019 11:56
- Forum: Feature Requests
- Topic: Calling a flow with arguments/parameters
- Replies: 14
- Views: 34506
- 07 Mar 2019 11:21
- Forum: Feature Requests
- Topic: Calling a flow with arguments/parameters
- Replies: 14
- Views: 34506
Re: Calling a flow with arguments/parameters
Yes, I know, but it's still not the same thing :) You have absolutely 0 control on a particular running instance of a flow, if that flow is called from multiple places (other flows). For example, I want to stop an instance of "Flow X" initially called by "Flow A", but from "Flow B", in the middle of...
- 07 Mar 2019 10:47
- Forum: Feature Requests
- Topic: Calling a flow with arguments/parameters
- Replies: 14
- Views: 34506
Re: Calling a flow with arguments/parameters
And how do you stop a particular running instance of a flow, if the flow is called from multiple places? How do you identify the flow's thread so you can act on it, without parameters which you can control, such as an ID, in paralel executions?
So you see, it's not the same thing.
So you see, it's not the same thing.
- 07 Mar 2019 08:45
- Forum: Feature Requests
- Topic: Calling a flow with arguments/parameters
- Replies: 14
- Views: 34506
Calling a flow with arguments/parameters
I think this would fundamentally change the way we build our flows: transforming the flow concept into a function, with multi-threading support. We can already pass to the calling flow some variables, but what about calling a flow with multiple parameters, which can be used to assign values to varia...
- 06 Mar 2019 22:45
- Forum: User Help / Bug Reports
- Topic: Multiple sleep() calls from multiple flows
- Replies: 13
- Views: 25615
Re: Multiple sleep() calls from multiple flows
If i manually execute all progress flows, this is how it looks like: https://youtu.be/zzgvFwvBB6s But the logs.. oh boy.. a concert of errors :-) Maybe Martin can suggest something? Reading about this error on the net, I'm unsure I can do something about, other than not to execute multiple flows wit...
- 06 Mar 2019 18:28
- Forum: User Help / Bug Reports
- Topic: Multiple sleep() calls from multiple flows
- Replies: 13
- Views: 25615
Re: Multiple sleep() calls from multiple flows
Here's an exception (and a screenshot with almost two simultaneous exceptions): 06.03.2019 19:50:51.530 [Volume20 Progress] Action 'Script: sleep(500);' java.lang.IllegalMonitorStateException at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(ReentrantLock.java:152) at java.util.concurrent....
- 06 Mar 2019 17:44
- Forum: User Help / Bug Reports
- Topic: Multiple sleep() calls from multiple flows
- Replies: 13
- Views: 25615
Re: Multiple sleep() calls from multiple flows
Here's a progress flow: http://automagic4android.com/flow.php?id=2cee0cd724661ce675472098062c6134d5cb898a I accidentally uploaded one for another widget, but it's the same for each, except for the widget name. I know it's a mess and ugly, but it's not meant to be shared. I'm try catching each action...
- 06 Mar 2019 17:30
- Forum: User Help / Bug Reports
- Topic: Multiple sleep() calls from multiple flows
- Replies: 13
- Views: 25615
Re: Multiple sleep() calls from multiple flows
Ah, ok :-D No, I took the ugly path of creating a progress flow for each widget. I'm not using one flow and pass variables to functions/flows as I'm normally doing, exactly because I did not want to start multiple instances of the same flow to avoid who knows what conflicts. But at the same time, th...
- 06 Mar 2019 13:32
- Forum: User Help / Bug Reports
- Topic: Multiple sleep() calls from multiple flows
- Replies: 13
- Views: 25615
Re: Multiple sleep() calls from multiple flows
I'm unsure what are you calling "glovar". Can you please rephrase or explain?
Thank you
Thank you
- 06 Mar 2019 07:18
- Forum: User Help / Bug Reports
- Topic: Multiple sleep() calls from multiple flows
- Replies: 13
- Views: 25615
Re: Multiple sleep() calls from multiple flows
There's no need to share, i think i got a perfect answer which makes perfect sense, many thanks for this precious info. The culprit is definitely the global lock combined with the sleep which is not part of the global lock and the queuing mechanism, which is also global, not per flow. Because of all...