Brokers often have limits. The EA is checking the minimum distance where SL/TP can be placed and if the requested value is lower, the minimum is taken. I think this is the better way, because otherwise you will get error messages such as 130 Invalid Stops
Take a look below StopLevel Minimum Distance Limitation here - https://book.mql4.com/appendix/limits
I'm here 
But give me more details about these problems. One of the reasons I don't like to answer to questions anymore is that for maybe more than 50% of the questions I'm missing the details and I have to guess what is actually happening and ask the person for more details. I like when the question is full and I can understand what the problem is in no time. It's perfect when I can also reproduce the problem easily.
Here from the question of the author I can only understand that there is some problem with .ex5 files. The title of the topic says that EAs stopped working. Only because some people reported that the new MetaEditor fails to compile some .mq5 files, I know that there is a problem with compilation. But the title doesn't say anything about compilation problems, it says that already compiled EAs stopped working. I tried that on my MT5 and I don't have a problem. So if this is the problem, again, I need more details. Error messages, whatever helps me to understand what is going on.
I also receive emails every day. I just fixed one compilation problem that happens when the new MetaEditor is used. But I'm personally using the .ex5 button and I don't see these problems, so I'm not even aware that they exist
I fixed it... I believe I will give you all some extra time
Ok, I made some updates and here is what we have now:
partial close at every 10 pips - https://fxdreema.com/shared/q1mwIcAQc
add to volume at evry 10 pips - https://fxdreema.com/shared/qrTOdbC0b
There is one big issues as well. Each "pips away" level is calculated from the open price of the previous trade that was made, levels may shift a little bit. I mean, let's say you want 5 levels with 10 pips in between... well, those 10 pips may not be exactly 10 pips
I think the reason why people dislike MT5 is the programming language - MQL5. Now MQL4 has almost everything from MQL5, but MQL5 doesn't have the easy to use functions that exist in MQL4. I obviously have some experience with MQL5, but even I don't like it. There are 3 things there - orders, deals and positions. And I don't mean pending orders. Those 3 things are so confusing. Every time I decide to do something, I have to once again remind myself what these things are. And now if you ask me what they are - I don't know, I forgot. It's really not a good experience writing code in MQL5. While in MQL4 you put OrderSend() with some parameters and voila.
One "Buy now" block makes 1 trade when it runs once. There are ways to make a block to run multiple times, but if you want to quickly make 2 Buy trades, just connect another one "Buy now". I wonder why you want to make 2 Buy trades at the same time, but I guess that I'm still trying to decide what you want to do. So I will say this again - if you want me to help you, make your questions as simple as possible and with all the information I need to know.
Actually the limit is far bigger than 2MB. I just tested a file that is 2.56MB and what I see is that it tries to convert it, the CPU goes high (which it not good), but it takes too much time to spit the result back and eventually it reaches timeout (I think its 30 seconds). On my local PC it succeedes, but it takes more than 11 seconds, and my CPU is quite good (i7-9700). Another file that is 1.74MB converted for 5 seconds on my local PC, and for 15 seconds on the server.
Right now not only I can't raise the amount of bytes, it seems that I should limit them to lower than 2MB. It seems that the speed of conversion is exponentially worse the bigger the file is. I will check what makes it so slow, but this code is kinda complicated and I'm not sure that I will be able to easily fix it.
About the links, I don't mind if they link to something good. When I made this website, initially I put links to it in 2-3 forums, so I understand that. If something is an obvious scam... no, thanks. I know both of you of you, Cam and l'andorrà, as people who have their own courses, and both of you know that I'm kinda like "Yeah, whatever, do what you want". Although I looked at Cam's link and it's not for me personally (I don't like those clocks and stuff), no one ever wrote to me saying that he is doing something bad.
If I am not wrong, this indicator have 1 output buffer, not 2. I feel that you want to do something like this: https://fxdreema.com/demo/mt4-buy-sell- ... conditions
I found 2 problems responsible for the slow convert and another problem that caused the data in the output file to be corrupted. I think it's all fixed now.
In few days I will upload NodeJS version of fxDreema, because I decided to use this platform and I rewrote the whole thing + I changed the database as well. The forum will be NodeBB, which is the only forum I can find for NodeJS New features... I don't know, even now people don't understand everything. Maybe it's better to make everything easier to work. Also, I think I have to write descriptions for most options in the blocks. I will also probably do some MQL4/5 code optimizator, because the generated output code needs to be cleared from unnecessary stuff.
When you look from EA's perspective, the chart in which it is opened is giving its parameters to the EA. For example, in MQL4/5 there is a function Symbol() that returns the symbol name of the chart. Also, the EA receives the ticks from the symbol of the chart.
But otherwise, you can open a trade in a symbol that is different from the one of the chart. The opened trade is in no way linked to the chart. And the way to do that is of course to write the exact name of the other symbol. It really should work if the variable named "fxname" is really a string variable with value USDNZD.
I looked into your last EA and I see that the variable has no initial value, but in Init it is defined like this:
Well, this sets the value USDCAD (assuming you opened the EA in USDCAD chart). I found one more place in Tick where you set the same variable in the same way (block 73). You have some Custom MQL blocks, but I don't see this variable there. So I don't really see where the value of this variable could become USDNZD.
I see that you are opening another charts with a custom code in block 311. But when you do that, I don't see how this changes the fact that the EA is still working on the original chart. ChartOpen() is just opening another chart, similar to how you would do it manually.
This forum is brand new even for me and I'm still looking at its functions. Yes, there are 2 types of pagination - by scroll and by pages. I also think that it's better with classic pages style.
Well, the parameters extraction happens on the browser and the code I wrote for this is not very capable, it doesn't really understand the MQL language. In this case I can see why the problem happens:
the code that I wrote thinks that the variable is defined on line 36 where this is clearly a string. In reality the variable is defined at line 20.
The correct values are:
data type => int
name => InpPeriodRSI
default value => 14
@l-andorrà said in "For Each Closed Position" block is not working.:
Yes, there ere some changes in the code a few weeks ago. You should use a new block in your projects instead of holding the old ones in your projects.
No, the blocks can stay the same, they don't need to be replaced with new ones. There is a situation when block replacement works, but this is when somewhere in its hidden properties (because they are all there, but some of them are hidden visually) some broken constant or a variable is lurking.
When I'm changing the code of some block, I prefer to do it in a way to not change it's assumed behavior. I only want to fix some bug or to add some new option. If I ever decide to really replace a block, which happened in the past, what I do is that I create a new block and the old one I deprecate. There is such functionality that when some block is deprecated, in the project where it used it appears darker and there is a warning message.
@ambrogio said in "For Each Closed Position" block is not working.:
@rafaelgrecco i tested your project in the strategy tester and it doesn't show the count, i replace the block "comment" with a new one, it works now
His "Comment" block is working fine, but he selected some dark colors and the text can't be seen on the default black background.
People were asking for stopping the EA for some time multiple times before and it's time for me to do something about it. It will be some block with name like "Skip ticks" or similar, and the idea will be that when this block runs, it will tell the EA to skip the following ticks for some time.
The same thing can be done right now as well, but with some datetime variable that needs to be set and then checked.
@roar said in When to stop OnInit():
Some event tabs have those specific filters, maybe the OnInit could have similar blocks too...
The problem with this is that if I want to add such blocks, I should remove this code and allow the whole OnInit() body to run always, which can change the behavior of the EAs for some people.
There are such problems everywhere in the EA builder where if I want to change or remove something, unexpected things could happen to many user's projects. And this is not like fixing a bug. If it's a bug, at least I can say "Yeah, but it worked wrong before and now I fixed it".
I think I should somehow make a whole new version of the EA builder, incompatible with this one, on a different link. Like 2.0 or something. Similar to how MT4 and MT5 exist in parallel. But I don't think I have enough breaking changes in mind to justify this.
I feel that every 5th person have the same trouble with multiple trades these days
Always remember this - when blocks are positioned under "on Tick", this means that they run on every tick! Well, those on the top.
Also remember this - blocks like "Buy now" create a new trade every time they run, every time! So the idea is to prevent these blocks from running on every tick. That's why we put those "No trade", "Once per bar" and similar stuff above them.
Exactly the same is true for "Close trades" block - this one would close trades when it runs, every time. So this one also needs some extra blocks on top... sometimes.
Here in this example the number of blocks is small, but still everything works fine: https://fxdreema.com/demo/mt4-buy-sell-buy-sell-opposite-conditions
@roar I had parthership proposals from brokers, and not only brokers, but I always decline. I'm very anti-parthership for some reason, so much that I don't even want to hire someone to do something instead of me. But lately, and especially after the hack, I started to realize that I'm probably not enough for this project and my strong anti-parthership shell is starting to crack a little bit.
But brokers... I look at them as the enemy, although without them this website would not exist.
