Page 1 of 1

I know this is not a bug but

Posted: 11 May 2020 09:15
by Hit
Can Dev add option for the Notification block to run immediately. Thank you!

Image

Re: I know this is not a bug but

Posted: 11 May 2020 14:48
by Desmanto
Automagic execute element per step. So if one of the branches delay the execution (including input dialog type action), all other branches are also halted. Ifyou need the script sleep(5000) execute at the same step as the notification, put another script : Donohting before the script sleep(5000). This makes them the same second steps from the first branching.

Re: I know this is not a bug but

Posted: 12 May 2020 02:29
by Hit
Thanks for your answer Desmanto!
But what I want is that each branch can run parallel (optional ON/OFF). I'm just curious if it can be achieved, because I'm having some idea to improve my flow. If cannot I will make an another request instead.

Re: I know this is not a bug but

Posted: 12 May 2020 03:10
by Desmanto
If in the same flow, no, it still need to follow the step execution. You need to put the elements in different flow and use execute flows from the main flow. You can have many parallel execution regardless the branches. Just make sure one branch is in one flow.

Re: I know this is not a bug but

Posted: 12 May 2020 04:12
by Hit
Yes, I have think about that before and have to create another flow for just one or two block
And if the two flows run parallel the variable in the second flow (the called flow) won't affect the variable in the first (the main flow) except global_variable

So there are two problems.

If my request can be achieved, I have two Idea for improving the application. Regard.

Re: I know this is not a bug but

Posted: 12 May 2020 17:05
by Desmanto
Too bad, but that is the way it works. I don't think Automagic will change this, as it will affect other users. You can create the flow in such a way it can be used by multiple flows, so it won't be a single one-trick pony flow.

To return the variables from the child flow, tick Wait for called flows to finish and return variables. You can call both flows at the same step, so both should have return at the same time. But between the child flow, you can only exchange data using glovar when they are executing. But upon returning, both variables are combined again.

Re: I know this is not a bug but

Posted: 13 May 2020 01:11
by Hit
I just say I want to add something not about deleting something and it's optional. May be I will make another request!

Re: I know this is not a bug but

Posted: 13 May 2020 17:42
by Desmanto
To clarify, you want that each branches execute immediately after it finish its, regardless of sleep or any dialog box that might appear. Is this correct? If yes, then this change will affect all users who already expect the branches will stop there. I have input dialog/debug dialog coupled with parallel control UI. I expect the Control UI will be stopped by the input dialog.

So if this is going to be implemented, I recommend it has to be per flow option. Maybe we can have something named as "continue branch execution immediately" in the flow option, default to "no". When this option for that flow is turned on/yes, each branch will execute on its own speed, just like a separated flow. I have seen several thread discuss about this, so maybe the addition of this feature can benefit some users.

I am not against any feature request. I just want that the addition of features don't interfere with our current flows. And Martin has limited time to develop new feature, so sometimes it better to look for workaround while waiting for the feature. That's why I usually suggest some alternative solution if it is possible.