Posts made by fxDreema

Now working?

There is a block called "Once per bar" and this block can pass 1 time per bar. Put it before or after the condition and the result will be different. There is no such thing as "on close of the bar", but if you have "Once per bar" on top level, it will detect when a new bar is created, it will pass on the first tick of the new bar. In "Condition" you can always set Candle ID to 1, 2, 3... or anything else to work with the previous candles.

The whole range is 50 pips, so +/-25 pips. Any trade. If am I not wrong I see that I missed to add some description of this block

I tried CFP and it gives my 0 with the default input settings that fxDreema reads, but they appear to be wrong. Well, not exactly wrong... The thing is that input settings are defined like this in the code:

extern int MA_Method = 3;
extern int Price = 6;
extern int Fast = 3;
extern int Slow = 5;
extern bool USD = 1;
extern bool EUR = 1;
extern bool GBP = 1;
extern bool CHF = 1;
extern bool JPY = 1;
extern bool AUD = 1;
extern bool CAD = 1;
extern bool NZD = 1;
extern int All_Bars = 0;
extern int Last_Bars = 0;

... and for bool fxDreema wants to see true or false, but the value is 1 and fxDreema thinks that the value is false. So, all of these are turned into false.

I set USD and EUR to true, then I tried this indicator in EURUSD and it works for me.

Well... ok. In this case "Trailing stop" will work only when the condition is true.

Ok, try it now. Variables must remain the same in case of changing input parameters, changing template or changing the chart

I know why, but I think it should not be this way. I will see what can I do for this issue

With so many input parameters there is a big chance for something to be wrong. Make sure that their count (in fxDreema) is the same as their count in the idicator itself. Also data types matter, but if all of them are like int, double and string, everything mush be fine with them.

And you probably have error messages if things don't work. Maybe everything works fine and you are thinking that something is wrong, I don't know. Show some errors if you have.

"Condition" only checks one condition. There is a block named "Indicator moves within limits" and I think it can be used, because you want to check if the price is between two levels. The price will be the indicator for this block and the levels will come from Fibonacci (Dynamic value) and by writing something in "Adjust". I'm not sure that this will work, but this is my idea.

"For each Closed Trade" - in the name of this block you can see the word "Closed", which means that this block works only with already closed, history trades. There is another block "For each Trade" that is working with trades who are currently opened.

These blocks are used to create a loop, but "For each Trade" can load the newest trade anyway, just set "Not more than "n" trades" to 1. Then in "Condition" (or other blocks) you can get any parameter of that trade in the "(in loop)..." category, which has pink icon.

https://www.mql5.com/en/docs/runtime/testing#time

__During testing, the local time TimeLocal() is always equal to the server time TimeTradeServer(). In turn, the server time is always equal to the time corresponding to the GMT time - TimeGMT(). This way, all of these functions display the same time during testing.

The lack of a difference between the GMT, the Local, and the server time in the Strategy Tester is done deliberately in case there is no connection to the server. The test results should always be the same, regardless of whether or not there is a connection. Information about the server time is not stored locally, and is taken from the server.[/quote:qdo9sokh]

You can also try something like this http://prntscr.com/9mmryd
http://i.imgur.com/m1FHrOW.png
The first block selects a group of trades that match the filter settings. Then for all of them in "Condition" some parameter is calculated (in this case, their total profit) and can be compared with something else. In the first block you can filter trades by "Group", if you work with groups. You can try with value like "1, 2, 3" which should filter all trades with groups 1 or 2 or 3. Or, you can try with market name as "EURUSD, GBPUSD" which should select only trades from EURUSD or GBPUSD. By default all blocks including this one are set up to filter trades with group 0 and market name as the one of the chart.

It will work. Data types are a little bit weird in MQL4/MQL5 and in the C/C++ world, especially floating numbers, but comparing booleans with 1 or 0 normally works.

You are obviously aware of the term "Group" in the EAs, but I can see your EA and this is what you have now - http://prntscr.com/9mmmci

So, the issue is that when working with groups, the group number must be written in each trading block - blocks who put trades, blocks who close trades, blocks who filter trades, blocks who select trades. Because by default all blocks are set to work with a specific group, which is 0 (empty fields normally mean 0). Yes, 0 seems like nothing, but behind it there is a specific Magic Number and as we should know, when we work EAs (even with one EA + manually created trades), this can be the only thing that maps certain trades for certain EA. Otherwise if the EA decides to close all BUY EURUSD trades, it will close all BUY EURUSD trades created manually, by the EA or by any other EA

This indicator has no inputs at all, there is very little chance to define it wrong in fxDreema But as a general rule, always try what the indicator is giving you on the previous candle (Candle ID = 1).

These warnings appear because of some additional checks in "Condition". Thei check whether one of the operands is equal to EMPTY_VALUE or not. The idea is to prevent "Condition" from activating it's outputs if one of both operands is EMPTY_VALUE, which sometimes happens with indicators or objects. Now there are warnings because the compiler can see that the operand always equals to true. I just don't have additional optimization of the output code to remove these checks in this situation.

Warnings are not scary in general. They are hints that something can be written better, but this is universal EA Builder after all and the code that it generates is not very compact and optimized, as you can see But it works most of the time!

I missed to check this link, but here is it:

This will help you understand how to manually fill inputs and buffers: https://fxdreema.com/help/-/working%20w ... indicators
And here there is more info about how indicators work in general: https://fxdreema.com/help/-/you%20shoul ... indicators

I must say that custom indicators are not included to the final file, only their settings are. So, the only difference between uploading .mq4 file or filling all the data manually is that the first way is easier and faster. And by the way there is no upload, no files are uploaded to the server, they are read locally and only the input settings are sent to the server

.ex4 files are encrypted and I can't read them, that's why their settings must be filled manually. The most important thing is to fill the inputs in their original order and count. If you add or miss some of them, the indicator will not work well. Their names are optional, but it's better if they are also the same. It's the same with data types and buffers.

I don't know, try something, you saw some examples. I obviously don't get the idea

Unfortunately I found the following problem. First, let's say I use strict mode and #property strict. It is supposed that by doing this, we allow MetaEditor and MetaTrader itself to tell us if our code is bad, that's fine. But try this EA with enabled strict mode (somewhere on the top, remove the // before #property strict) and this is the result:

https://fxdreema.com/shared/wY4sLJf2d
http://prntscr.com/9lf1sh
http://i.imgur.com/LrC3Sue.png

What this EA does is to create a trade so Equity of the account can change over time and then I just print it's value with using NormalizeDouble.

Print(NormalizeDouble(AccountEquity(), 5));

So, even if I use NormalizeDouble, the value appears as not normalized at all. %(#8040FF)[AccountEquity()] returns "double" value: http://docs.mql4.com/account/accountequity. **NormalizeDouble **is supposed to work over "double" value, but this is the result

This "Endless line" is the option called "Ray". But even on the chart the trendline goes to infinity only one one of it's side. Which side... depends on how you draw the trenline. Trendlines are drawn by 2 points, so try to swich them