Posts made by fxDreema

Note that the Group number must be filled in all trading blocks - Buy now, Check..., No trade... all blocks that works with trades from this group

Sorry, it should work now

I tried this one - https://fxdreema.com/shared/qYJUcK36e - without Group and with Group = 1 (as it is now) and in both cases I see the same backtest. Maybe you can give me some similar example that shows the problem? I can see your project, but normally I people's projects contain many extra stuff and I don't know where to look for the problem.

As I know, comments can only be set in OrderSend when a new trade is created and then the comment can only be changed by the broker. Trades and orders unfortunately don't have custom tags, which is very very limiting. I don't know, maybe something with the lot size? I actually never thought about that, I never needed to separate child trades. Or maybe you can use the Group number

Pretty much the same idea: https://fxdreema.com/forum/topic/4231/add-to-volume-and-close-partially
Mother and child trades look like different trades, but they have have something in common. I think that Open Price or Open Time (or both) in the child trade is the same as in the mother trade and that's how I can find their relationship.

Why do I believe that I answered to this question already...
Get some idea from this: https://fxdreema.com/shared/EutATUU4b

Trailing stop blocks should run on every tick, their place is not under Buy now or Sell now - https://fxdreema.com/demo/mt4-trailing-stop

@MetaTrader PM function?

@shomefun Maybe something like this - http://i.prntscr.com/6b00c543e0ba4f3ca48f6ea343e7ed24.png

I feel that every 5th person have the same trouble with multiple trades these days

Always remember this - when blocks are positioned under "on Tick", this means that they run on every tick! Well, those on the top.

Also remember this - blocks like "Buy now" create a new trade every time they run, every time! So the idea is to prevent these blocks from running on every tick. That's why we put those "No trade", "Once per bar" and similar stuff above them.

Exactly the same is true for "Close trades" block - this one would close trades when it runs, every time. So this one also needs some extra blocks on top... sometimes.

Here in this example the number of blocks is small, but still everything works fine: https://fxdreema.com/demo/mt4-buy-sell-buy-sell-opposite-conditions

People were asking for stopping the EA for some time multiple times before and it's time for me to do something about it. It will be some block with name like "Skip ticks" or similar, and the idea will be that when this block runs, it will tell the EA to skip the following ticks for some time.

The same thing can be done right now as well, but with some datetime variable that needs to be set and then checked.

Don't you have this gray magnifier icon up near the bell icon? (I don't know why it's gray)

If every day of the week is false and you have 1 block "Weekday filter" on top of all other blocks, then I guess this block will be checked on every tick, but those below will not work. So it should be as slow as the "Weekday filter" alone. At least this is on theory...

In the past I was analysing the speed of the code many times and I know that MQL sometimes behave stupid. Imagine you have function with 30 rows of code, but with "return" on the top which basically means that the code below will never run. Well, I noticed that sometimes only the presence of such dead code can make the EA to run slower. Imagine what is going on with 1000s of rows of code

When optimizing, I think there is more from that stuff. And to be honest, I don't know what to do with these situations. I wrote several times for such problems to MetaQuotes before and most of the time there is no answer or they do nothing about the problem. Only once they fixed something.

You are here for a looong time, I even know your name. Why don't you take some time to learn programming basics, it's not that hard to understand variables, if, for and functions. This can only help you in future

Otherwise if you have function like this, you basically hit that "New" button near "Custom functions" in the studio and throw that code in there. Then you should be able to use this function in the blocks.

I admit that I don't understand security very much. Maybe if you define a empty "string" Constant and then in "on Init" you have something like this.... https://fxdreema.com/shared/Rh6tjQqEd But how secure is the string on the right side in "Condition", I don't know

Because there is a block for that: https://fxdreema.com/demo/mt4-trailing-stop

Well, the EA only says to MetaTrader "please, open this many lots with such SL and such TP" and then MetaTrader does the rest. And when your account currency is different than any of the second part of the currency pair, then don't expect direct connection between pips and money.

I can see you are doing your own calculations for lot size, SL and TP. I don't know why, because there are many Money Management options available anyway, but what can say... It's probably something that is not calculated properly in all these Formula blocks.

Are you asking for what is known as Trailing Stop?

You tried the Trailing stop block? There are many options in it.

I would use the "Adjust" field, you can write things like +2pips in it. No need for "Formula" blocks and variables for such thing.

If this EA should work with manually created trades, better set this to 0: http://prntscr.com/dgm3pd

I don't know what else to say. "Condition" block normally compares 2 values and one of its outputs becomes active depending on the result of that comparison. When crossover (x> or x<) is used in "Condition", then it's almost the same, then the "Condition" is like 2 in 1, because there is one more hidden extra comparison (for the previous candle) to determine crossover. There is no matter what is the result of the comparison, "Condition" block DOES NOT sit and wait for some condition to become true. This block can do 3 things only - to run the next blocks connected to its orange output, to run the next blocks connected to its yellow output, or to do nothing at all.