Posts made by fxDreema

I don't really understand the question, and on the picture I can see many sell trades... I don't know, I am confused

Warnings are not fatal, errors are. These are only warnings... mostly annoying stuff.

By default it should work the same way + by default it is limited to 1 arrow per bar. There are 2 options at the top that controls how the arrows are created/updated. So they can be created on every run, once per bar, once per bar and then update the recent arrow, single line and then update it.

Here is how to create a new arrow on every run of the block: https://fxdreema.com/shared/Cxz8rIjHc
Both options on the top are No. The result is the same as in the old block.

Ok, I will say it again - I don't hold the key for this problem, this is MetaTrader problem, not fxDreema problem. You have the code, you can see that the input parameter is defined as it should. The EA does not have more control than that.

That "Migrating from MQL4 to MQL5" topic is more than 4 years old! It came out when they launched MT5.

I think the backtests are done properly, the only problem is that the time does not appear in a human readable format. Well, after all, there is no such thing as H1, D1 and so on... for the program everything is numbers, and for example 16385 represents H1.

Done, you can test it

I got the EA above and here is what I did:
http://prntscr.com/4m78ph
http://prntscr.com/4m792w
This is part of the code: http://prntscr.com/4m79mo

I also found this: http://www.mql5.com/en/forum/14406

I don't know why on my side it shows values like 1, 2, 3. It seems that for example PERIOD_H1 equals to 16385

Also look at the function on the top here: http://www.mql5.com/en/articles/81 It shows the values of all "PERIOD" constants.

Well, in the first case the EA is looking for certain conditions on the current candle, which is unfinished. What you see at the end of the test is not all the information.

"Once per bar" also works, depending on where it is placed. You can also try with different Candle ID parameter (for example 1).

Here is how the crossover works in "Condition" block: https://fxdreema.com/documentation/proj ... er%20works

I'm preparing some new "Draw..." blocks, including brand new "Draw Arrow" block where the name can be defined by the user

I don't know. The code looks fine, if something is wrong with MetaTrader... To be hones, I don't do optimizations very often

So, as I explained it above, some things will go away when you remove the EA, others will stay. If we take the Martingale block for example, it checks the last closed trade's lot size and doubles it for the next trade. So, in this case Martingale does not start blank. Most of the money management methods are like that.

Here is some example: https://fxdreema.com/shared/bkV80cXlc
Result is here: http://prntscr.com/4m1fer

Why are these values like that? 16385, 16386, 16390... these does not belong to the ENUM_TIMEFRAMES enumeration If I am not wrong, PERIOD_D1 is 86400 or something that can be divided by 60.

My idea is to put "Delay" block under "on Init", to wait for some time before the EA actually starts to work. Well, if that time is not too big... Or something like this: https://fxdreema.com/shared/COJ842m7e

Mm, I think I've done it, can you try it? It now checks if the trade is opened after the EA is started. If the trade is older, the block will not pass.

Parameters of trades and orders = lot size, type (buy, sell), magic number, sl, tp, open price, close price...

I think the problem is in "once per trade/order" block, as it uses temporary memory to store the tickets of all trades. When you restart MT4, all information about this is cleared.

I think I just found easy solution for this and I will try to fix it, but a little bit later because now I have to so something I will let you know...

Many things makes the EA slow. Mostly in backtesting, you should not have any problems live. Yes, fxDreema is build to be universal, some blocks have multiple properties and in the output EA you get all the things you need + even more things you don't need. So, the same EA can be coded manually and it can be more optimized. In the same time it also depends on how blocks are connected, you can have the same strategy results with different blocks (or the way blocks are connected) and one can be slower than the other.

Let's say you want to check some indicator between 17:00 and 18:00 only. You can place the indicator before the time filter, or after the time filter. The first block will work on every tick. Well, the time filter is most probably the faster block, so if this is the first block the strategy will work faster. If you connect the indicator condition first, and then the time filter, the indicator will be running on every tick, whole day long, but it will be slower. The same result, different speed.

Constants and Variables are just regular variables for the EA, which are always used, they are not making it slower. In fact, there are times more variables in the EA other than these you define in fxDreema.

I don't know your EA now, I lost track. But when you build some EA, always try to use parameters of trades and orders - they will be there when you restart, they will be there even if you reinstall MT or move to another PC. For example, let's say we want to make Martingale. We can create some temporary variable and store every next lot size in it. When we restart that variable will be blank. But if we get the last lot size from the previous trade, the information will be there even if we move to another PC.

F3 global variables are a way to keep some information for later use. Almost the same as writing it in a file and then read it. The information will be there after you restart MT, but not if you move to another PC

Well, someone else will prefer the EA to start clean on restart. I think these global variables (from F3) will do it if you need to save some values for later use, you tried them?

No, the white text on the chart cannot be edited, this is past from MT4 that cannot be controlled from the EA. Otherwise I'm preparing some blocks to draw different things on the chart, including static text that can be controlled.

I think I am missing something. Here:
http://i.imgur.com/jjIIDT3.png
block 11 should pass only if close a trade manually or with block similar to "Close trades" (not by sl, not by tp), but in your logs I see notifications when trades are created and then closed by tp You are showing me logs from the same EA? Block 37 is the only e-mail block.

Also I don't get what "blahblah()" means.

Yes, always check EAs on live demo! That slippage problem is bad, but no one complained about this before. Now I understand why in some situation it can be better to first send the trade and then set it's stops. Well, now by default when we send a request to create a new trade, we send SL and TP as price levels, not as values relative to the open price, so...
I can suggest this: http://prntscr.com/4lnl2w

I tried Terminate block, it works for me. Try this block alone.

I believe that these errors comes from the e-mail part, maybe something is not properly configured to send e-mails. Do you receive any e-mails? More than that, look at the message that says "allowed 10 messages per minute".

I don't like S/L and T/P levels for some reason. You have trades closed on TP with loss... slippage or what? Can you check what is going on under "Experts" tab? You should find some messages like this: http://prntscr.com/4lf4rg Look at mine spread meter, it is 2.00 and my trade is just fine - sl 124 points (12.4 pips), tp 40 points (4.0 pips).

Are those conditions fine? I mean, do you get the proper values for the Candle Close and that indicator? This should be ok, if not... I don't know, check the history for missing data in H1