Posts made by fxDreema

You have <If some trade exists> on every tick. This will not create pending orders by itself, because there is no trade initially. But even if you have some trade, it will start creating unlimited number of pending orders, because the trade is running and on every tick you create a new pending order.

So what you have is an endless loop which (fortunately) cannot start, but if it ever starts...

Try it in the opposite way, with "No whatever exists". In this way you create trade/order when it does not exists. And then, after it is created successfully - it will not pass the "No..." check again.

Also you can check the number of trades/orders if something like this is needed. "No..." is checking if 1 exists.

There is also "on Trade" event, but if you can do everything under "on Tick" it will be better. Because the Trade event is fired ONCE when something happen, while "No..." block is basically a condition that does not depend on events.

I gave you examples 2 times already in email, what about them?

By "days" you mean days (multiple days) or day's (1 day only)?

https://fxdreema.com/shared/yIANUzMIc

To check if something is = or > than something else, use Condition block. Indicator rise and Indicator appear (and other blocks from Indicators category) are something like multiple Condition blocks in one.

I told you that such a mess is bad, here is the same thing (I hope) with some order: https://fxdreema.com/shared/zP3UMbSPc
Export .mq4 file and import it in your profile to work with this project.

• When you only need to separate buys from sells, there is no need to use groups. Use groups when you want to separate buys from buys and sells from sells.
• I don't know where the trailing stop should be - after some conditions or working directly. I used *10000 to convert ATR values into "pips", because there is no "price fraction" option at the moment in trailing stop block.
• Something is wrong with blocks "Buy TP as sum" and "Sell TP as sum" - they calculate take-profits, but trades are all created without any stops initially, so these blocks don't have the chance to pass.
• In blocks 46 and 66 I used "Trading model" reversed with *(-1) in both cases.
• atr_stop_buy_grid and atr_stop_sell_grid are now defined, but not used.
• I didn't tested all the possible situations, but I edited many things and there is a chance for something to be wrong somewhere.

I'm not sure about that. Normally the EA receives OnTick (and other) events for the currency where it is added on - when a tick comes for the current currency, OnTick() is executed.

In theory, if you really want to control all currencies the same way under the same EA, you should have some infinite cycle to detect tick events by all currencies. And this is not impossible, but when you have to work with some currency, all the others will wait. This is called "blocking".

Actually I don't know what will be the behaviour of such an EA, I never tried this. This is something that I had an idea to make, but it's still only an idea. I guess that if you have multiple EAs they does not wait for each other.

Well, MT4 cannot backetst multiple currencies by itself. Otherwise you can create and manipulate orders from another currencies, but being under the ticks flow of the current one.

Oh, I forgot about this one
Fixed on the web version and reuploaded as build 086. But be careful with these select values.

And very hard to do actually. As a programmer in the beginning I was exactly like that, everything was chaotic. It is very easy to fill the program with stuff at the beginning, the problem starts after that. It's really bad when everything is spaghetti and some problem must be fixed or something new must be added. I fix something... something else crashes. I update something... it's getting even more chaotic and also something else crashes.

Now I'm training myself to make some order, and basically that's why I'm not updating fxDreema very often. Well, also because people don't ask for it, because there are already too many things for them. But I have some updates in mind that I want to become true.

I reorganized visually one of your projects before just to be able to understand it, I know that is possible

You can get information from the 3rd trade if you are sure that you want to work with it, here is an example: https://fxdreema.com/shared/Et6KuJiXc
Here the orange output of "For each Trade" can be active at most once, no matter how many trades there are, it just loads parameters of the 3rd trade from the currently running ones.

If you want to load 3rd trade which is sorted not by time of creation, but by something else, then the things are getting complex. Well, "For each Trade" can sort them by profit, look at the "Loop direction" parameter.

Damn, this project has now too many variables, formulas and flags. I think it needs reorganization, some areas with descriptions.

With so many global variables and start points (blocks connected only from their output) out there, blocks numbers matters. Blocks with lower number are executed first. Maybe this is the problem.

Organize this stuff somehow, make some order. I will spend more time getting basic idea of what is going on

It looks visually good now

But again, you have "No trade/order exists" on the top and below "If... exists". If some trade or order exists, blocks 10 and 14 will not be reached at all, because block 1 will not allow it.
You can have 2 separate chain of blocks - one for buys and one for sells. If this is the idea of course. So it will be like that:

• No Sell trade exists -> Condition to Sell -> Close trades -> Sell
• No Buy trade exists -> Condition to Buy -> Close trades -> Buy

How to check conditions... I use "Draw arrow" most of the time. Place this one under some Condition and on the chart you will see tons of arrows on the place where the Condition is true. You can also check 26 and 27 this way.

To check values, like indicator buffer... and any other numeric value, use "Indicator tester" block like this: https://fxdreema.com/demo/mt4-indicator-tester

https://fxdreema.com/demo/applying-or-logic-method1
https://fxdreema.com/demo/mt4-or-logic

You don't need these "AND" blocks. Also, one of them is connected to itself, this will cause problems.

Now you have blocks like "Close trades" below block "No trade/order exists". If there is no trade, there is nothing to be closed!

I still think that you expect the top block to work first, then wait until the one below does it's job, then wait until those below.... It's not that way! Look at this example: https://fxdreema.com/demo/mt4-wrong-closing-rule It's a little bit different but it shows that idea and you MUST get this.

__
If I do the automatically set , can I change it in the middle of the run ? for example if EA is already set to buy only , can i manually set it to sell only ?
[/quote:3aoo7yl0]

Try it.

__
about top to bottom. I want EA to count from top to bottom in range like 8 candle days , or 12 candle days.
for example .... eurusd price bottom at 1.5000 and going to swing major top at 1.8000 . I need to count how many candle days from the swing bottom to swing top. Is it 15 candle days or how many candle days. I need to get that info. Then I will calculate that info for projecting the next reversal day. Something like that. I'm planning to make the swing top or bottom from the zig zag indicator. Or perhaps how many days from the oversold RSI come to overbought RSI.
[/quote:3aoo7yl0]

So you are searching for the ID numer of the candle where the last top/bottom was? I think this is a job for some indicator. If there is some object placed by the indicator on the place where the last top/bottom was, you can try something like this: https://fxdreema.com/shared/EjZVBNHcd
This is searching for the last arrow object with certain properties (red color) and then getting it's Candle ID and using it somewhere.

There are blocks for trailing stop - one for each trade individually, one for group of trades... and also for another situations. ATR gives you values in that format which I call "price fraction" or "digits" (if there is something not updated by me somewhere). You can try these.

In block 15 I can see you are using constant, which is... constant, remains the same. Or at least it should remain the same, better don't try to modify constants. This is the only block before "For each trade", so if there is some problem with running "For each Trade", I think the problem is in this block.

I don't understand everything you say, but I can see that now you have some project like this:

No trade/Order exists -> If Buy order exists -> Sell now

When you don't have any trade and any order, there is no way that you can have buy order at the same time. So you get nothing, these blocks are exactly the opposite.

"AND" is not needed.

I don't understand what "top to bottom" means, but I have this feeling that you expect events to happen one after another from the top block to the bottom block. It's not that way, the event is "on Tick", those blocks are running on every tick: https://fxdreema.com/demo/mt4-wrong-closing-rule

No. There is only 1 function that controls this text: http://docs.mql4.com/common/comment It is what it is - no font, no color, no size.

It is possible to put text on the chart, like this spread meter on the lower left side, but I have no block for this

I transformed it a little bit so I can understand the structure better... https://fxdreema.com/shared/pJh3SS0pb

So the problem is not in blocks 185, 186 and 187, it is in blocks 184, 180 and 181... depending on which one is used?

Then I think the problem is this. Variable "grid_space" is the difference between two price levels, let's say 1.5 and 1.4, divided by 20. Now, 1.5-1.4=0.1 and 0.1/20=0.005. Variable "grid_space" is a value similar to 0.005. I call this price fraction, difference between two price levels. The problem is that "pips away" blocks accept pips value, something like 10 or 20 or 30. I can add option to accept price fraction, but... you know, at the beginning I wanted to add as many options as I can, but now I am the opposite Well, if you do grid_space*10000 I think it will work.

I actually have special functions to conver these values, but I will not recommend to use any of these functions, because I can eventually change them in future. In other words, I will not support these functions. So the value 10000 is accurate for most markets (symbols), and if you really want to make the EA symbol-independent, then there is a function toPips()

MT saves last used parameters in ini files somewhere, so when you add the same EA next time it uses the last input parameters used. But you can always see what the input values are