Topics created by reyxv16

@reyxv16 Are those pending orders too close to current price? Then the problem is with your broker for programming to close to it.

I found the problem, there was a block of custom code that apparently was not saved correctly and therefore showed the error.
I have solved it by deleting that block, I can already access the account.

No, I personally don't like advertisements of any kind and I can't force myself to think about this, it's too complicated for me 🙂

I added a new block "Order moved" under "on Trade"

Solved, I think the problem was a custom block that was modifying, after removing the custom block and re-creating it with the same name the problem was solved.

All Ok

Oh, I think I know why this happens and I will go to fix it now. It may take a while.

For projects with only few blocks it might generate bigger files than before, but for bigger projects it makes them smaller. But it was not only because of the size, MetaTrader does not complain when an EA is megabytes. In general, it's better when a code is written in OOP style and I wanted to do that for a long time. Although, now that I did that, I can't say that I really like this style, it's probably even harder for somone to understand what is going on in the code.

Sorry, it should work now

I don't even know what are vectors and matrices in MQL4/MQL5. Arrays are very limited in my opinion, I always have problems with them.

Custom blocks are made from here: https://fxdreema.com/studio/
It's enough to write some code and it will work. To be able to connect with other blocks there is one keywort ~next~, put this where the next block must be run. All blocks are normal functions in MQL, so ~next~ will simply be replaced with function calls while building the project. ~inext~ is similar, but for the second yellow output.

Here is some screenshot: http://prntscr.com/9fhqoo This is the code for the "Draw Button" block.
At the bottom you can see ~next~. Use this block in a project, connect some other block after it, generate the code and you will see with what ~next~ will be replaced.

As I mentioned, each block has it's own function in the code. The parameters of the block are local variables in the function and they are automatically generated and put at the top of the code. So in the code you only use their names directly, as you can see in the screenshot.
But there is one specific parameter ObjText that is not used as a variable name. Instead, ~ObjText~ is used and this puts it's value directly at that place. I do this for parameters defined as "Custom", because this parameter is actually a function and it can be anything (custom indicator and so on... ) and I don't want to run this code at the top, because in most cases it will not be used. It will appear in the final code, but there is a chance that it will never be used.

Here is another screenshot: http://prntscr.com/9fhtss
As you can see, it depends on StopLossMode whether ~dpStopLoss~ will be used or not, the same for ~ddStopLoss~ and ~dlStopLoss~.

At some point I will make the generator to remove those parts of the block that are not used, but for the moment this is the situation, most code from the generated EA is never used.

You can also define functions and there is no need for explanation here - just hit New, write some function and save it. Then use it where you want - in the custom block's code or even in the blocks. The generator will find that function and embed it into the final code when it's detected.

How to define input parameters... well, I think you can learn it when you try it. This "--" button creates separators - those things that are used to group parameters. If the parameter is a drop-down (as in the second screenshot), then for each of it's value you can select few other parameters to be shown.