Posts made by fxDreema

The best way is to create some Constants (you can see Constants on the right side) and use them inside blocks. These are basically "extern" MQL4 variables. See here: http://fxdreema.com/documentation/proje ... 0variables

Magic number is attribute of every trade/order, and the idea is that different EAs can share the same pool with trades and orders without interfere each other.
Every EA created with fxdreema has at least one input parameter called MagicStart, which is magic basically number. More here: http://fxdreema.com/documentation/proje ... d%20groups

Very nice view of the question by the way

"Clear all objects" on deinit?

Well, you can search if there is a trick to do that. I remember that once I searched for this and didn't found a solution. If you ever find indicator, ea or script that can write such a thing, show it to me

Aaaand putting this into the pending features list. Now you can try to use the custom indicator in Condition - built in indicators - Custom indicator. I think it will work.

Putting this into the pending fixes list

Every object is created with ObjectCreate(), then modified with one or more ObjectSet(). But I'm not sure that rechtangles can look as you like in MQL4 In MQL5 there are more properties and I think it's possible there.

And by the way, I think you want to create an indicator. Maybe the right choise is to really do that. Fxdreema can't help much, but at least I think it's funny (that's why there are many indicators around).

Init can't be escaped because each block is enclosed in a different function, and with putting "return;" in a block you actually escape the function created for this block, but not the main "init()" function.

EA builders are good to quickly add/remove things like Buy, Sell, Close and similar. When it comes to variables manipulation you are searching for troubles with every new block that is visually bigger than the variable itself
Now you have a big net of blocks that do very simple things, and in that case it will be better to write all this in MQL4 code

Colors updated.

I'm not sure about the border you want to draw.
This is the function to set properties of objects: http://docs.mql4.com/objects/objectset
And this is the list of properties that can be set: http://docs.mql4.com/constants/objects/properties

__
My goal is to track and close the Price Channel 3 pips below DowChannel order buy, and 3 pips above UpChannel order to sell.
[/quote:h199qyy9]
To track and close you don't need to extend the current SL with 3 more pipe on each bar. Why don't just... track and close? Track with "Condition" and close with "Close each trade".
In "Condition" put "Ask" or "Bid" on the left side and that indicator on the right (or the opposide). To add or remove 3 pips from one of operands, use it's "Adjust" field. To add 3 pips, write "+3pips", otherwise write "-3pips".

If you really prefer to use SL, you can use "(in loop) Modify SL and TP" with the indicator inside. Again, use "+3pips" and "-3pips" in Adjust field. But I think you have to use 2 blocks of these and separate buys and sells with "(in loop) Check trade/order type".

I can suggest:
Start trades loop => (in loop) Shrink SL and TP

Ha, never thought that someone will ask for integer. I can do something for this later.

In any case, this seems to work:

double shift=1;
double output=iOpen(NULL,0,shift);

"(in loop) Extend SL and TP" is a block that modifies SL and TP of the last loaded trade ot order. It requires "Start trades loop" block to be placed before it, because this block is designed to load existing trades one by one.

I didn't tested it in that way, but probably "(in loop) Extend SL and TP" can work right after Buy now or Sell now. But you better use "Start trades loop".

__Build correctly. But some appeared more external parameters, as shown in the screenshot below:[/quote:2jde7z4p]
Most of the blocks can show/hide parameters when you change some mode. When parameters hide, they are still there, but invisible. Everything appear in the output code, but part of all is used. This is how it happens at the moment.

I can suggest to put "Once per bar" (two of them) below the Condition blocks and remove the one at the top. This will wait for crossover until it happens, even at the middle of the candle, not only on the first tick of the new candle.

This is what I got on my backtester. I have no real account to put it to work, and it will take time in demo, but you said that the same problem happens in tester as well.

I wonder what closed the second and third buy on the last picture, because it's not the SL obviously. It is the x< crossover probably, but there is no Sell at the same time. And without errors...

I can also see that the color of the close arrow for the first Buy is different than the color of the close arrows for the next Buys. Is this backtest really? Please, don't put many EA's to work at the same time with the same magic numbers.

This is the same strategy with control Alert messages, so you can follow the strategy and see where it does not work as expected: http://fxdreema.com/shared/1pkvcT49e

......
crossovers.gif

I guess this is because of the Trailing stop that you use. It's settings says to place SL to 25 pips when the trade goes above it's open price... which for many trades means almost immediately. See "Start when profit is above" parameter of block 8.

It looks like very normal EA, and the project is very well made. Do you have some error messages in "Experts" tab? And do you know if the EA reaches the point to trade (blocks 7 or 16)? I wonder if the problem is in trading blocks or before them. I can suggest to put "Draw arrow" block on dfferent control points of the project to see where it's working and where it's not.

This can not be done in fxdreema at the moment