Topics created by kroghd

This is how it looks on my side: http://prntscr.com/7w75jm

I also checked it for MQL5 and on the local version. I don't know what you are using - EA generated weeks ago or old local version, but in both cases there is one common word - old.

Thanks

Perhaps you can have the best of both scenarios e.g

If condition adjust value contains variable name - replace variable name with ToDigits(variable_value_here,CurrentSymbol());

Else
Check & replace like you currently do

Hi,

I am running local version - time problem was a web one to show you an issue.

I will prepare an example project & share to you so you can simulate.

Thanks

Hi,

In the project variables - for your output into the mql file can you allow it to support just the variable name declaration.
Because if I don't supply a value the MQL file will not compile as your output is assuming all variables will have values.

datetime MyDate =; fails build

if no value consider output as:
datetime MyDate;

Thanks

I did that. Thank you for noticing this bug in the code 🙂

Yes - I meant to say I have put Print() custom mql4 but after some time they stop getting run.

I will try with the comment blocks and see what I can figure out

Someone wanted to be able to use any data types (and enumerations), so I removed the available options. But I also added some basic description for data types below. The most important are int, double, **bool **and string

I think I fixed the problem, here is what I used to work with it: https://fxdreema.com/shared/iXmqBbmAc

I don't remember why I decided to set SL to it's minimum size in AlignStopLoss() while working with virtual stops. Maybe because I wanted the same EA tested with normal or virtual stops to give the same results in backtest. Now I make it the way you want it and I hope that there will be no problem to come out of this 🙂

I will try to fix the other things as well.

Well, I updated the web version. Additionally, I reuploaded the local version with this fix, but my updates does not affect older local versions that somebody have... the local version has it's own local database 🙂

Pips away from TP - means, that it detects when the price is at some distance from TP. For Buys, this is when the price moves down at some distance from TP. The current price for Buys is used to be Ask, so the formula you show obviously operates with Buys. Then when we do TP-Ask, because TP is above ask, the result will be positive and we are serching for that. The opposite Ask-TP will be negative and... not the one we are searching for, because on the other side we probably have positive value (if PipsAway is positive).

Get the local version that I reuploaded or try it on the web. At least I can see what are you doing on the web.

Well, the closed trade has "parent" trade even if you close it for the last time. To resolve the problem I added function to get the "child" ticket, so now there are 2 checks. I think purple blocks are enough 🙂

@adakco No project is visible.

Fixed on the web version 🙂

The next build is up already 🙂

My fault, it seems that settings are not updated at all. I reuploaded 082 now, you can try it. I'm currently working over trailing stop blocks, but I'm not finished... so if you notice problems with this now, tell me... just saying 🙂

Ah, you are using the local version? Ok, I reuploaded it now because of other small problem with another person (081), you can ty it.

This block puts the code that you enter in a function. It's not impossible to close that function at the top and open new one in the code:

} void MyFunction() {

or even call that function:

MyFunction();} void MyFunction() {

But I will suggest to try https://fxdreema.com/studio/MQL4
There you can define custom functions that can be called in the project (if something is not wrong, because I didn't tested that soon) in the low right corner where "Custom functions" are.

I think I can't find that function for CORNER_LEFT_LOWER 😕

Only 1 value can be used for Candle ID, and I don't think I will do something about it, at least not in Condition 🙂
Maybe "Indicator moves within limits" can be used for this, because it checks each candle. Normally it checks some indicator for each candle, but candle parameters can be considered as indicators, so... not impossible.