Posts made by fxDreema

Yes, everything should work fine. Well, there are still some differences in the input parameters of some indicators, but I can't really help that.

If it works, you should not care. These 0 things are there to prevent compile errors when no condition is written, then the condition becomes 0||0, which is false

@4tronic You have few projects edited lately, for which one we are talking about I don't particularly understand this "Open new Trade in same Candle should only be possible if the Market price is 10 pips below Closed Price". You open a trade on the current candle only, because opening a trade happens in the current moment. But the current candle doesn't have "Closed Price", because it is not closed yet. Technically it has "Close Price" that is the current Bid, but Bid is also the current market price. So how can the market price be 10 pips below itself...

MetaTrader shows you where the pending order was created (the first arrow) and when it was triggered (the second arrow). So you have 2 blue arrows connected with line. This is how pending orders normally look in the Tester, I don't see something strange.

Well, in the "Bucket..." block you have few filter settings to select which trades to load, so instead of combining you just select what you need. What is different between those 2 groups of trades? If it's the Group number, for Group # write something like 1,2 (both group numbers separated with comma)

So, the EA would try to open the requested lot size, but I made it in a way to open the closest possible lot size instead of giving error messages. So I guess that for your broker the minimum lot size is 0.1, the EA detected that and opened 0.1 lots.

I guess that you output information from this block:

Instead of Text, navigate to Numeric. The idea is that you want to output a numeric value.

Do you actually have the .ex4 file? The only reasons for the "Start" button to not work that I know is that the file is broken or missing. Can MetaTrader read the file is my question

I decided to rewrite the function that creates and removes the virtual stops. I tried few variants and I can't decide which is the best one. The one that is the best logically and allows for less possible problems is unfortunately very slow when backtesting. So I think I will use this variant, but when testing the EA will turn off Virtual Stops and will work with normal stops instead. This is actually the case now when optimizing, because the Tester doesn't work with objects (horizontal lines...) when optimizing.

So, if you backtest the strategy, will you get the Buy trade at that place again?

Oh man, if this is the simplest example that you can make... Don't you see how lazy am I And do we really need like 10 different groups of trades. Every bug is something small and simple and the key is to make it happen quickly and easily. I really imagine something like 5-6 blocks at most. Every single time I want to fix a problem, I end up with less blocks as possible, even less than 5.

What is the whole idea of this project? I don't really like those different group numbers and so many "For each..." blocks. As a programmer, I can imagine the "for" loop in each of these blocks and if so many "for" loops are written one in another in a single document, I know that something is very wrong and it's better to be reworked.

I don't understand very well

You know how Martingale works - you buy 1 and you lose, then you buy 2. So every time you lose, the size is multiplied by 2. After profit, you don't need to multiply, so the value is 1. You can change the values if you want to change it. For example, the Anti-Martingale strategy is the opposite - you multiply on profit and reset on loss. With the default values you have the original Martingale.

There is already one input parameter called MagicStart that sets the magic number. This parameter is automatically created for all EAs. The name "MagicStart" is a litthe bit stupid, it means that this is the magic number and "start" means that you start with this number and if in the EA you are using Group numbers bigger than 0, the actual magic numbers of the trades will be bigger that MagicStart.

For me these rules are absolutely stupid. Even if the idea is for the people to become more aware about the information they provide, I don't think there will be such effect. The only effect is that people will be annoyed from these messages and in the future they will care even less.

Obviously this website collects nicknames and emails. I can see people's projects and I say this in every other topic. When someone has some problems in one of his projects, I look in that project to see what the problem is. Even if someone tells me that he has a profitable strategy, I won't use it for anything, as I don't care about trading in Forex anymore. I also never traded with EAs, I have more than 10 margin calls only from manual trading

When someone makes a payment, PayPal or FastSpring are sending me information of the person that includes his name and address and I keep this information for no particular reason in the database. The same information exists in PayPal and FastSpring anyway, so I have it even if I don't want it.

You know, those block number are not looking good anyway. Some weeks ago I believe I fixed one problem that caused blocks to suddenly receive such a big numbers, but who know, maybe there is another problem somewhere. So I will suggest to try this:
... and then check if everything still works, just in case.

I think I fixed this now

I can compile and export your latest project at least. It takes something like 4.22 seconds, but I got the file.

I don't know if you are using the plugin for downloading in Chrome, but if you do, then try to reinstall it. I know that sometimes it breaks for some reason, it happened few times for me before.

If you can repeat the problem, tell me which project and what blocks do the problem. You can also export .mq4/.mq5 file and import it again in fxDreema to create a copy of the same project, in case you want to continue working on the original. I will then investigate the problem over that copy

https://www.mql5.com/en/docs/basis/variables/inputvariables
Here somewhere on the bottom sinput is explained.