Topics created by ekanters

@ekanters Sad but true. 😞

@l-andorrà I guess the problem is in block 83 afterall. No problem in MT4 but will check it later in MT5

@roar Maybe I can repeat the modify stops somehow. I will look in to it and find another way. Will let you know.

@ekanters 😉

@ekanters Good. Please share his reply here, if you don't mind.

So I need to get used to MQ5 tester because just saw in History all trades did close which is not visible in operations. But that still doesn't explain why the EA does not terminate with "ON TRADE" settings.

0_1557061874402_fill.jpg

@fxDreema The problem was indeed in Pass Once ID's. The example bot can be found now under TestVer 3.0 Thank you very much because I can now move to the next phase whatever that may be. 🙂
0_1556273118262_v3.jpg

I think there is a bug and I will fix it

SOLVED 🙂

Solved it was an error on my side. 🙂

That's why you see this title - Constants (Inputs)

now you are demo milionaire 😄

I don't understand the idea of this group 1-2-3-7. From what I see, it doesn't prevent the group 5-9-11 from working.

It's a long story...

In the beginning Variables were just regular global variables and Constants were "extern" global variables. Then I started thinking "Hey, what if I remove the Constants and put a checkbox to turn any Variable into "extern" parameter?". And obviously I did that. But immediately I found a small problem...

In MQL5 you can define "extern" variable and then modify it in the code. But in MQL5. Try this MQL5 code:

input int inp = 0; void OnInit() { inp = 1; }

It can't be compiled, it says "'inp' - constant cannot be modified"
If I use "extern" instead of "input", then there is no compile error, but also the variable is no longer an input parameters, it's like the keyword "extern" does nothing for MQL5.
Only in MQL4 and only if you use the keyword "extern" you can have input parameter that can then be modified into the code. But this behavior is for legacy reasons.

So, having input parameters that can be also modified in the code was (and still is) forbidden in MQL5 and even in MQL4 (when you use "input"). That's why after I added those checkboxes for the Variables I almost immediately regretted.

What is the situation today? In the output code of the web version of fxDreema, both Constants and Variables are not global variables. They are members of two separate classes. This means that they all can be modified. But there are some problems again. I found that for people with many many Variables, the code is compiled very slowly. I guess that having classes with too many members is not good idea. So I'm now thinking to make Constants and Variables global variables again.

There are some technical difficulties as you can see and this determines my decisions 🙂

"Solved" Its working and the exact profit amount was reached. But its the exact same bot as before (apart from arrows) So I think somehow a lot of old and wrong info remain when changing stuff. In this case I think It used data from the copied sell bot that was used to build the buy bot. Anyway "SOLVED"
0_1489077885147_buy.jpg

Solved. I love you. 🙂

Nice, I try that. Thanks

The problem is that pink blocks does not work in this "combined" mode that you want. The first block is called "For each Trade"... just look at it's description. It says "for each", not "load all", this block creates a loop for each available trades and runs the next blocks multiple times. There are also some examples in fxdreema.com/examples.

"check loss" checks the loss of a single trade at a time. Look at this topic, I just answered to a similar question viewtopic.php?f=2&t=3307

Try this

http://i.imgur.com/S49muwA.jpg