Topics created by drayzen

Of course there is difference. This block checks whether MA8 is between the upper and lower level. Imagine that the upper level is the upper line of Bollinger Bands and the lower level is the lower line of BB. Then the block passes when the indicator (in your case MA8) is between both levels for the specified candles.

Yep, that's got it sorted, thanks. 😉
Always check the obvious...

What I know is that in MQL4 the function OrderClose() allows you to set the lot size to be closed, which makes the function capable to partially close the trade. When that happens, in the list of trades it appears that the original trade has been fully closed and a new one has been created (with smaller lot size). Both trades have different ticket numbers, so visually you can't even tell that it was a partial close, but it's a little bit different on a lower level. I'm not sure, but I think that it's better to partially close the trade instead of fully close and open smaller amount after that.

Yes, fxDreema Variables.
The thing is I've built an EA that trades the 28 majors and crosses in a single instance (one chart).
So there's potentially a lot of trades going on if I load it on multiple timeframes (one chart per timeframe).
Want to be sure they're not going to get confused with one another...

I'd been thinking about it a little further, and I'd expect that Variables would be restricted (essentially sandboxed) by each chart, but would like confirmation.

There is an example of enum here: https://fxdreema.com/shared/TRSxAxdmd

Well, the block is called "Indicator rise", so the idea is that the value for every candle is higher than the value of the previous candle. If you want some candle to be lower, then there is this "With exception of few candles" option.

So you can check the spread in a regular "Condition" block. I'm not sure whether the "Spread filter" block is slower or faster for the tester, because it has some more options, but you can test it and choose which block to use.

Oh, yeah, that connection is not very clear in my picture

I found that this option didn't worked and I did some updates to fix it. Maybe something broke visually now, but in any case this option is only for x> and x<, so the fact that you see it under > is only a visual bug. Which is an old bug I think, I knew that something like this happened from a long time, but when I decided to finally fix it I forgot how to cause the problem. Now I know 😄

When you select Custom (pips), the expected value is some number like 10 (for 10 pips), not 0.0010. The difference between Ask and Bid is not that kind of a value. Work with Custom (price fraction) instead.

ok, so it's function is essentially 'Cross on any of n Candles'.
... still trying to think of anything I would want that for, it is obscure. 😉

So if I'm understanding you this means a setting of 4 = C3 OR C2 OR C1 OR C0 = TRUE
I could actually see an inverse use for this to filter out low volume "noise" crosses by it returning FALSE for n > C0, while still returning TRUE for only C0 = x>/x<.
e.g. Cross Width (Filter) = 4
C1 OR C0 = FALSE
C3 OR C2 OR C1 OR C0 = FALSE
C0 = TRUE
But again, it's would still be a bit quirky, I'm guessing finding a separate filter method would be more efficient, or could a Cross Width (Filter) = 20+ work efficiently?

Forget all that, just found the Indicator moves within limits block which covers that application. 😉

ok, so turns out it was just me thinking 'Once per bar' is smarter than it actually is.
My thanks to @fxDreema for taking the time to explain it to me.
I was thinking that it would continue processing until something connected to it passed, instead of the actuality of it being a 'dumb' block that just passes on the first available tick and doesn't care what happens after that.
Rebuilt to this https://fxdreema.com/shared/s8DnMJDKb ... and everything is right in the world again! 😄
It's actually surprising it worked as well as it did with the incorrect setup...

I will fix this. The lower option is for that Status thing, yes 🙂

I just tried deleting and reloading the custom indicator again, and now it's loading the same as for you.
I don't know why it was like that, I previously tried re-adding it a few times but it was always the same.
I notice I've also got a colour for the Output Buffer while it was blank before.

Just ran in in MT4 and worked perfectly, matching exactly against manually inserted indicators.
While still a bit slow, much faster than before. 😉

btw, my optimised backtesting so far gives Periods 16 & 48 as good for EUR/USD H1 (Though 48 was the maximum).
I'm going to add a 3rd McGinley and optimise with wider parameters...

I was thinking some more about the custom indicator issue and it could be that I was using Firefox before and have now switched to Chrome as recommended.

@drayzen said in Is this ok?:

I get a lot of errors in the Journal which I have no idea what they're meaning, and for some reason it's got a Variable in MT4 inp10_VolumePercent that I have no idea where it's come from...?

I only have an idea what these errors mean. They are not because of the EA, but because of the ticks data. You probably know that MT4 has data for each timeframe - M1, M5, M15 and so on... When you are testing on H1 let's say, data from lower timeframes is used. But sometimes we have periods of missing data and I think the problem is because of this. It could be something else, I don't know how exactly the backtest works, but the problem is for sure because of the quality of the ticks data.