@miro1360 yes repaint..I sure......

Give me example.

But Martingale by definition is supposed to work like this: You bet X money - you lose - you bet X*2 money - and so on. And by "bet" I mean buy or sell, NOW, not later. Also only 1 trade at a time. Everything else is just assumption made by me. This behavior that you are talking about, maybe it was intentional. I don't remember exactly.

Also note that when Martingale looks at what will be the next lot size, it looks at the latest CLOSED trade. But before that - at the newest running trade (which again is not by the rules of Martingale and I made it to work that way only because of some people that wanted to play not by the official rules). Pending orders are not checked at all and I don't feel like doing this 🙂

Well, I have no idea why. This forum is new for me and there are things about it that I still don't understand 🙂

Here is about the objects, I tried to explain them via those 2 examples https://fxdreema.com/examples#Chart-Objects

now you have in tutorials small answer for doji, you can improve it in your project 🙂

@miro1360 thx vey!!!

Double TP on loss? There is no direct functionality to do this. All Money Management methods are working with the lot size. So I guess you need to check the profit of the last trade before opening new one, get TP of that last trade and use it in the new one (x2)

Remember that the EA must work for this. Expiration is natural for pending orders and happens on the server, but expiration for trades is not. The EA monitors the time on every tick and decides when to close the trade.

If you want something like 2 strategies in 1 EA, you can set this Group parameter which is on the top of all trading blocks (Buy now, Trailing stop, No trade and all similar)

I think, If there is an open trading and i work editing on EA and replace EA occur messier in sequence , I try it without edit works properly.
Thank you, genius 🙂

He selected H1 for Period, the EA itself can be set to work with the current timeframe, whatever it is. In the blocks you can specify H1 (in Timeframe parameter), this is your choice

#define .... This is not a buffer, this is just a constant definition that is available in the indicator only.

input ... These are the input parameters. Each one of these must be defined in fxDreema.
Now, there are some issues that can cause problems:

Here...

input int barSizeInTicks = 100; // Bars size (in ticks) double customBarSize = barSizeInTicks * Point();

barSizeInTicks is an input parameter, but customBarSize is not. It only appears in the middle of all input parameters, which is kinda bad structure. Don't add customBarSize to the list of input parameters.

input MaMethodType MA1method = Exponential; // 1st MA metod input BufferDataType MA1applyTo = Close; //1st MA apply to

MaMethodType and BufferDataType are defined inside the indicator file. If someone knows how the EA can see these, let me know. But I don't know. What I know is that the EA don't have a clue what these mean. The EA knows only those data types and enumerations that are defined by the system (that exist in MQL natively) or those defined in the EA itself. But the indicator is a separate program that connects with the EA via some function called "iCustom".

So, instead of MaMethodType use "int". The possible values are 0, 1, 2 and 3, but not Simple, Exponential, Smoothed or LinearWeighted.

Again, if someone knows how the EA can see those enumerations in the indicator, let me know.

Well, I don't recommend using functions that I have made, because eventually I might change them and they will stop to work. When I do things, it happens that I always rethink the way I did them and I always change something here and there. So, use any of my functions on your own risk and be prepared for that EA to broke eventually 🙂

"missing" numbers are not important, important are only top blocks numbers, this is how is connections order working:
blue is order, and next colors are blocks runned in each blue order:
0_1484164228379_upload-21b5ef27-0a10-4172-8bb2-2693e263b502
somewhere in help you can find next explanation for this ...

and the blocks what you mean as "hidden" are not hidden, it are normal blocks in fxdreema, but they are only renamed (right click - rename) (I left original name in begin of this block) .... only "Custom MQL4 block" is little special, because here you can type own "math" or some functions, working with variables in text, etc. ...

@doperthancereal said in Trading only on specific days:

Just made a thread if this helps
https://fxdreema.com/forum/topic/4284/weekday-filters

thanks it help

Hi Does anyone know the answer to the above? The formula to set the variable for the ATR stop loss works on a Buy or Sell now. However why does it not work on a pending order? What if you don't want a trailing stop for it? Thank you

This is not a restriction from fxDreema, the problem is that at least I don't know how to read .ex4 files and extract input parameters from them. MetaTrader can do that obviously, but when you upload indicators, they are not even uploaded. The file (.mq4) is read by the browser, parameters and buffers are extracted from the code and then sent to the server. Because fxDreema needs only them. But if you open .ex4 file with text editor, what do you see 🙂 After all .ex4 files must be secure and this itself is a good reason for MetaQuotes to make them hard (or impossible) to read

thank you for your time

@miro1360 Thanks Miro will keep looking. I can see how to do just the single action but combining them for a single rule is where I am stuck. No worries thanks for response.