What is specific for the trades that must be closed? Use that specific thing as a filter and close them. In "For each Trade" you can filter by group, type, market, time, you can also sort them by profit and select how many trades to work on, and also you can skip some from the list that this block creates. Under "For each Trade" you can also filter by something.
Do you understand the need of "For each Trade" and how this block works with the other pink blocks in the same category?
The probability is that you would find the problem while building the test environment 
I don't really know the idea. The block "close" closes whatever is loaded from the "For each..." block above. If you run this block outside the loop, it will also close something, if it still exists.
You want to request a server for data, then you must know what keys and values are acceptable and in which way - POST or GET. Then, getting those values in the EA is... test this with the block called "Comment on chart".
What trade amount? Do you own the server you want to request?
Haha, it's not that I am looking at pools to decide what to do next. For the indicator builder I want to rebuild fxDreema first. I started this process months ago, now I think I am somewhere at 75%. A big part of the work was to create my own PHP framework, which is a totally different project by itself. There are PHP frameworks out there, but I always want to do everything myself And meanwhile there are other things to do. Not to mention what happens when I get lazy, but this is normal for home based work
And in fact the indicator builder is not my passion, I'm thinking more about some EA backtester, because I'm so tired of MetaTrader sometimes.
What, it is difficult? I do this every day to show something to someone, or to check something for myself. At least this is refreshing.
This is Area #2 is not exactly right, but it's not wrong as well. The "close" block will close the right trade, only because you have 1 for "Not more than....". The yellow output of all "For each..." blocks is the end of the loop. At this point there is some trade/order loaded and blocks like "close" will do something over it. It is the last trade/order that "For each..." block was loaded.
What means "jerky" and what are these other programs?
By the way you don't need "Once per tick" and "AND" blocks, and now I'm gonna hide those already.
There is no way to delete a buffer, but the EA does not care even if you put 1000 buffers. Buffers does not have names, they are numbers (the first one is 0), so whatever you write there is ok. These names are only for fxDreema, for you to see something meaningful when you open the indicator in "Condition".
Now you can't connect blocks between tabs only because you can't see them at the same time. And if it is possible to make connections like this, how the connections would look like?
Now I even have ideas to make it possible to use multiple pages (tabs) within the same event tab... to group blocks somehow, something like Areas. This means even more tabs. I always prefer to see everything on the same page, but sometimes it's good to put some order
I'm giving you old versions of fxDreema that will probably work with the old MT4. This does not mean that I will do something for these versions. Whatever blocks and options I'm going to add now, they will NOT work for 509 for sure.
__Fine that you found the problem.
Giving block a real name and not only a number is in my opinion a very good idea!!!!! 
When you also wan't to remove the IDs from the vision of the user then how can I jump from one block to another when they are not connected.
Example: I have some functionality at the 'on chart' tab and when I initialize the EA I need to call that functionality within the 'on init' tab then I won't have any chance of calling the blocks at the 'on chart' tab and have to copy the whole functionality to the 'on init' tab!? I won't have any 'GoTo' functionality!?
I really would love to see the names IDs stay ! I was so happy to see that I can jump to another block on another tab that makes the EA better readable and gives it more structure!
Hope you let the IDs stay.
thanks
hila[/quote:3nihl69m]
People don't understand what happens when they have parallel connections. Sometimes they even connect blocks in parallel when it's easier to connect them serial... then I explain about these IDs.
Another problem is that at some point numbers become big numbers. Also when you have many blocks and there is no order, it's hard to find certain ID. And there is a title that can be edited, why not using this?
For "worm holes" maybe it's better to have special blocks with special IDs, or why not colors.
There was a guy who suggested a block with multiple inputs and multiple outputs 3 years ago, to be something like matrix. But again, people don't get some simple things, what about such a fancy stuff (this is only more material for me to support)
Got it. The problem is a little bit below on the code where I get the ID of the block and put it as is, and if it numeric there is no problem, but in this case the ID is DrawGui and this is not recognized as a variable
But I really think that I will remove the option to give blocks IDs like this, and I'm thinking of how to hide them, so they will remain for the system. Which block will run first (in parallel connections) will depend on it's relative position to the other blocks - the first to run is the one who is on the right/on top. What do you think about this idea?
There is a block called "Condition" that was made to do the "if" stuff. It has 2 operands, left and right, and for each one you can find this place called "Adjust" and write something in there. Better read the description of this block. Hold your mouse over "Condition" and you will see it.
There are also blocks to modify things. Also check https://fxdreema.com/examples
But before everything, get rid of this 509... or find some other EA builder that was abandoned, because this one does not work with it anymore. It worked for some months after build 600, but now I'm moving forward, it's almost 1 year later. Now I use functions that are only available in 600+ and I'm not gonna rewrite it only to support some old and worse version.
I think that everything works. Now you have some errors in the block with the custom code.
There is a function "fxD_BlocksLookupTable()" that is used to support blocks "OR" and "AND", and because of that you are able to see human-readable variables mixed with number IDs. Long story.
I will say this again: I will not support old MQL4 code. This is in the history, does not exists for me anymore. PipValue does not exists anymore, this code does not exists anymore.
The web version of fxDreema can compile the EA, it has the latest compiler, but the .ex4 file will not run on 509 anyway.
At least 600+ is faster. It has many other features for MQL4, but if not else, it's faster to backtest. 509 is history, and not only that, it is a history that was slower. Just do something to install and run something new.
There is a block called "close"
I will not support older versions of MT4. Why? Because after build 600 there are many new functions and I started to use them in the code. You can't compile it because MetaEditor sees functions that does not exists for it. Build 509 was the last build from the old era of MQL4, now MQL4 is a little bit different, so... install something new somehow
Woooooow, this one is OLD! And there are major changes after build 600, so everything before that is useless, it will give you errors and I will not support it.
Try whatever it takes to install and run the newest MT4 version, or at least something that is not older than 6 months.