Posts made by fxDreema

https://fxdreema.com/index/desktop/download/fxdreema_install_build_100.exe

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

2400 blocks? You know, I think that the compile error is the smallest problem here. 2400 blocks is... ok, I mean that even 100 blocks are too much. And I don't know how to explain to you that 2400 blocks most probably mean very bad design and everything needs to be redesigned anyway

The error is because it should be like this:

if (StringLen(symbol)>6 && StringSubstr(symbol, StringLen(symbol)-2)=="bo") {

It comes from the main function to create new trades and orders. It's interesting that people report it more than 1 year later. The compiler that is inside the desktop version seems to work with it, but not the newest compiler (Meta Editor). I guess I need to do something about this, but there is some chance for something else to broke if I make another desktop version from this old age

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

You can try to give that constant data type of ENUM_MA_METHOD instead of int

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)

Can you work with the age of the trade, which is time between now and the time it was created? In this case you are using values that stay in MetaTrader even if the whole PC restarts.

There can be other tricks, like using Terminal Variables (they are stored in some file) or even objects on the chart. But if you can just work with the age, that will be best.

I don't think strings can be optimized. Yes, you can always use the other method (component) and there you have each value separated and integer (numeric, it can be optimized)

Right click on the block and you will see

What does the blue line mean... https://fxdreema.com/demo/mt4-wait-crossovers I wanted to make this functionality for so long, then I made it.. and then I realised that it's probably not that helpful. I don't use it and maybe one guy used it once, so you probably don't need this at all.

Because the SL level is fine, but the TP level is not. 10000 means something. But you don't have initial TP, so try with 0 instead

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

Different blocks use different type of parameters. This is mostly because I made these blocks in different times and my ideas were different

If you are talking about the Money Managelent method, try to group trades with the Group number, maybe this will help

https://fxdreema.com/forum/post/15503

#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

On all charts together - you probably want to use the account profit (equity, balance). These are available in Condition - Account. So you can check what is the account profit and then use "Close trades" to close some trades... or all of them.

Only when you want to get profit out of some trades only, but not the global account profit, use "Check profit (unrealized)" or some other block from the same category.

To check the profit for each unique trade, then use "For each Trade" and pink blocks.