Posts made by fxDreema

Too many buys and sells sounds to me like logic issue. If we take the EA from the picture above, it depends on what timeframe it is added, and the result will be as many trades as many bars are created. Well, if the timeframe parameter in "Once per bar" blocks are set to "Current".
So, this EA creates new trades based on time. It does not care id there are some at the moment, it just works from time to time. This is not wrong normally, but if you don't want to do it that way and it is that way - then it's wrong.

Reuploaded under the same build number, so if there are problems - tell me.

I don't know how it will be on your side, but I got error messages somewhere in Chartobject.mqh file ("cannot convert enum"). If you have them also, add (ENUM_OBJECT_PROPERTY_STRING) before OBJPROP_TEXT so it will be like this:

//--- result
   return(ObjectGetString(m_chart_id,m_name,(ENUM_OBJECT_PROPERTY_STRING)OBJPROP_TEXT));
  }

Well, by "Does not work properly" I understand that the problem can be everything. Define "Does not work properly"?

Yes

I choosed to group trades and orders using their magic number. There are no many options actually, the only parameters we can use for something like this are Magic Number and Comment, but the Comment should be available for the user so what remains is the Magic Number.

So yes, that Group number is connected in some way with the Magic Number and you can create trades with certain Group number and then use trailing stop set to trail only those trades with that Group number. Here is a little bit more about this topic, I hope you will understand it: https://fxdreema.com/documentation/proj ... d%20groups

I think you should look here some of the basic examples http://fxdreema.com/examples
Especially those that has name starting with "Wrong"

Look at what really happened. It looks to me that something is wrong, like if all trades are closed immediately after opening.

It looks that this parameter http://prntscr.com/3e71yj is not ready to be used as an input parameter. Because it's not a value, it's a sign (< or > or == or something else) that is used directly in the code. Just uncheck it.

Well, I tested it (build 080) and I have no problems with it. Can you upload .mq4 file here? It can contain only this block and some other, there is no need to be a whole strategy.

I see code error here, this is not a logical error. Something is wrong in the output code, some ) or } (or other MQL4 part) is missing somewhere. Can you tell me which block causes this to happen? Also what if you use the same block, but as a new one (with all default parameters)?

__FxDreema....

Is an indicator builder something you would consider adding?[/quote:3tnt0t8f]
I know it will be great if there is an indicator builder as well, this is also one of the oldest requests. I don't want to lie to you, I don't know when will I start creating it, there are also many other things that are in my head from long time ago

My problem with indicators is that I don't understand them very well (because I was never interested in them) and I don't have very good picture in my mind how a custom indicators builder should looks like.

Otherwise I also have some features I wish to have:

• Pages - ability to show groups of blocks in pages, similar to those events above. Maybe it's better the project to be in pages, where you decide what event to associate to every page. Or maybe it's not better.
• Own backtester. In my greatest fantasies MT4 and MT5 are not used at all and everything is backtested in some integrated backtester. I want that because very often MQL4/MQL5 is not enough for what I want, but wha'ts good in MQL4 is that it is based on C++ (or it was only C?) and it supports dll imports.
• Ability to use Condition-like option (somewhere called Dynamic or Custom) everywhere instead on the regular input fields.
• I want most of the blocks rewritten
• Multilanguage support. This is very old request.

And other things.
Now I'm stuck a little bit, but I started to create my own PHP-based framework from scratch and I will probably rebuild fxDreema over it. I guess it looks that I waste my energy in not important background things, but when my code is not good I always reach some point of complexity where I can't continue.

Look in "Journal" for error messages, because I see some error message above about the history data. Otherwise start with normal backtesting, not optimisation. Optimisation is... it depends, you should know what you are optimizing, and by the way it does not show the results of all tests.

I checked this block, it looks fine. What do you have in it's parameters, and are you sure the problems comes from it? The problem is that somewhere something is not closed, missing ) or } probably, which leads to multiple error messages.

There are some MM options... well, not documented... but you can try them. This one that is "Freeze..." calculates the lot based on the current money. "% of..." is something based on my idea and works for currencied like EURUSD - it is when you have 10000, the lot size is 0.1, when you have 20000 the lot size is 0.2 and so on.

It depends. There are blocks like "Buy now (Martingale)", or lot size can be controlled outside "Buy now" in some variable.

https://fxdreema.com/shared/xb3p8xpMd

Remove MQL4\Experts\ from the path?
It should be what you get when you go to File->Open Data Folder in MT. Better with \ at the end

The terminal path should be where MT4 is installed, where the compiler is (mql.exe), but now there is a chance that you don't have that file anymore, so it will work if you select any existing folder. In this case fxDreema will extract mql.exe from itself and will use it remotely.

Oops, I forgot that. You can read the topic here in this forum which is on the top - Where is my .ex4 file? I can't answer in one word because it depends on Windows version and MetaTrader version, and also on fxDreema version (so use the latest).

These blocks like "Draw arrow" are to be used when you have some problem and you don't know what is it, or to know where you are and what is going on. If you know what the word debugging means At least I'm doing everything that way - I do something small, then check if it's working... then I add another one and I check again...

Now block 9 can be executed twice in a tick. If that is not problem, fine. What happens now is that block 7 is executed and if it's condition is right - block 9 is executed. And then block 8 is executed and if it's condition is right block 9 is executed again. So, if you want true OR, use the OR block... there is an example somewhere in http://fxdreema.com/examples