Posts made by fxDreema

I tried the very first variant +VarName pips and it works for me. It turns the value of 10 to 0.001 for EURUSD

Find this block "Check profit (period of time)"

Sorry, I saw this question, but I forgot to answer to it

It's hard to say why this happens. In my backtest I see many pending orders that expire quickly, maybe the broker doesn't like that. Do you have more error messages?

Which project is this? I see another kind of error in the project that is currently active, which is because you have 1 Constant defined, but you didn't specify type for it. I can see that this type should be whole number, which means that the type is int. But I see another problem also - for the input field where you placed the Constant, you also checked that ckeckbox on the right side. Uncheck it, it's not needed when using a Constant.

Again, there is no predefined constant or variable called Point in MT5. Yes, Point is valid predefined variable in MT4, but it doesn't exist in MT5. It is _Point in MT5, or you can use the function Point()

As a Type for the Constant write this: ENUM_MA_METHOD

If you look in "Condition" block, in "Market properties", you can find this "Highest Price (Time Period)". I think this can give you the price you want. Also there is a "Lowest..." version. You decide whether to out trades or pending orders.

But how can you get information from multiple accounts at the same time in the same MT

So you are saying that the block doesn't work as it should? I will check it...

Also there are custom indicators for this. I knew that such indicators exists before making this "Pivot Point" option, but people asked again and again for it, so I decided that they probably don't always need to see the actual lines. But if you are using such indicator, its lines look better.

Where do you put that? In MQL5 I think there is no predefined variable Point, so I guess it is available to be used.

When you import a file, the language (MQL4/MQL5) is decided while you are doing that. I can't remember exactly... maybe because of the file extension of the input file or most probably by getting information about that from the embedded project information.

When you generate .mq4/.mq5 file from fxDreema, the project data is embedded at the end of that file and it looks like a big comment with letters. Then when importing, this data is read only. And in that data there is information about the language.

If you want, you can have MQL4 project, copy its blocks and paste them into a new MQL5 project. And then check that everything works, because there are few differences here and there.

The old desktop version I think still works the old way, which was that a global variable will be automatically created after the Formula block. So you only need to write a name for that variable, which is always automatically written as something like ResultXX.

Can you show what you tried? In the EA builder up in the menu you can find an option to make a shared copy, then you will get a link and post it here.

All those options in "Account" are basically list of all "Account..." functions in MQL4/5. I don't know for a function to test ping.

I don't know, this looks to be like a job for some indicator, because normally indicators are those programs that make calculations and produce signals, while EAs are mostly taking those signals and creating/closing trades and orders.

Once I tried to write some code to automatically put trend lines like that and possibly get some signals from that, but it was a little bit complicated to me and I abandoned it I still have this idea, because I think that trendlines are something very common in trading, but I don't know how to do it best. I guess there are indicators out there, for example I remember some by name TrueTL. I never tested it, I only remember it as a name and that it does something with trend lines.

Fixed and ": " is now added automatically

I tried this indicator and it looks that it is giving me the right values. What exactly is not working?

MagicStart is the only parameter that goes in there automatically for all EAs. It is like this from the very beginning.

Oh... this anchor parameter is confusing for me as well. I mean, it probably doesn't work the way you expect, but it works right. If you have doubts, look at the value of this parameter in the output code... if you can find where They are 2 possible values - ANCHOR_TOP and ANCHOR_BOTTOM.