Posts made by fxDreema

This is a warning, not an error. I fixed this warning, but it was not a problem anyway.

Interesting. This function iBars was not present in MQL5 as long as I know and that's why I defined it. On the server the compiler I use is a bit older and that's why it works. On your PC MetaTrader is the newest version and maybe they added this function lately, although I can't find anything about it in the documentation.

I don't remember for a MQL function that can "hit" on that button. But what you can try is to start with "Pass" block on the top and then use "Turn OFF blocks" and "Turn ON blocks" to toggle it. If you are using these blocks, better give the target block (that "Pass" block) some short word instead of its number.

In the same EA, Martingale works for the same pair, yes. You can have let's say one Buy and one Sell blocks (or more than two blocks, it doesn't matter) working on the same pair, and those blocks will work "together". Basically, before going to create a new trade, the lot size is calculated from the previously closed trade with the same Symbol and magic number (or Group #). So if you have another block for another Symbol, then it works on a different Martingale... instance.

You can't get a local variable out of the block. Take a look at these Bucket blocks https://fxdreema.com/examples#Bucket-of...

Once per bar can also work for particular timeframes, let's say 4 hours.

In blocks 23 and 29 try x> and x< instead of > and <

@mojios, bitcoin you say?

Today I uploaded few fixes again

I added a new block "Order moved" under "on Trade"

I think it works for me if I make it 2018.4.15 00:00

Which project? Error messages?

In "My Indicators" you have this:

I think this will not work in the EA. You can try to define those variables above, before the first "enum", but I'm not sure that this will work either. Or if you know their actual values, better use them directly.

@drayzen It is string, but I'm not sure that it will work. This particular parameter is a little bit more special

If "Once per bar" works, why do you want to use the other block. "Once per trades" can be confusing, at least for me it is very confusing. This block is very rarely used, I almost forgot that it exists

Is the problem still present, because few days ago I uploaded some update? The problem was not very easy to investigate and I'm not sure what else could be wrong now. There was a problem in the function where I detect the type of "Trade" events. Basically I count the number of orders, deals and positions and decide whether something new was created or removed. MetaTrader 5 is unfortunately very very confusing and every time I feel that I'm hacking it instead of using the rules from its documentation. Everything is very strange. These problems happened because outside the Tester, when you are doing "modify" of a position, the count of orders changes few times... and this never happens in the Tester, something that I never knew.

But for you, I think that you better make the EA with partial close instead of these rules.

I don't have block to read data from files. People asked for such block many times in the past, but for whatever reasons I never made one

I'm using Google Translate to translate this, but it is not very good with Spanish. So I'm not sure what is your question. If you are asking whether I make custom programs, I don't

I guess that you have modified version of this example: https://fxdreema.com/demo/mt4-buy-sell-buy-sell-opposite-conditions So you probably have x> and x< in the Condition blocks and these signals happen only when there are crossovers and not in the rest of the candles. So you can close the Buy trade few candles after it was created and the EA will still wait for the next crossover.

To close the trade by Stochastic, add something like "Condition -> Close trades" in separate branch or put it inside the existing blocks somehow.

More details?