Do you want "on Hold" event?
-
These days I was playing with this idea. And the idea is to hold on blocks until they pass. So, if we have "Condition" somewhere and it is reached, but at the moment it is false, on the very next tick to run this block directly and doing this again and again until it passes.
Why do I want this... because many people want to do it like this, like the way that is wrong in this example: https://fxdreema.com/demo/mt4-wrong-closing-rule
And I did it it 2 ways. It's interesting how the EA should behave if there is more than 1 chain of blocks. I decided that the best is if each chain of blocks is independent from the others and I now have this working, but the problem is that with all the control points that I have added to make this possible the result EA is working really slow
-
I can see a 'hold' option being useful to help visualise an EA on screen but the more I use your software the more I find there are many ways of achieving the desired results and I'm finding it's simply me needing to get my head in gear and think logically. So yeh a hold option could make some things easier for some people who as you said like to link blocks one after the other but isn't entirely necessary once you understand more how to use the program.
-
Another way to the same thing is to be able to allow to put some blocks on hold under "on Tick". But I decided that it's better to have a special working field for this feature. Everything is actually very simple if only 1 block can be on hold at a time, it's easy to stop the whole EA until particular block passes. The problems starts when I decide to allow multiple blocks to be on hold at a time, and more than that - to allow chains of blocks to be independent from one another. So, if some group (chain) of blocks is on hold, there could be another group (chain) of blocks that works for itself. Now the things are also becoming aynhronous and probably unpredictable. Even I have hard times thinking in asynchronous mode
