Posts made by fxDreema

There are options to filter trades - which trades you want to work with. Trailing stop (each trade) works on multiple trades when executed, all trades that match the filter settings.

Trailing Stop = the distance from the current price where SL should be kept
Trailing Step = the minimum step at which SL should be modified.

For Buys: SL is modified to Ask-Stop when Ask>=SL+Step+Stop
For Sells: SL is modified to Bid+Stop when Bid<=SL-Step-Stop

... where Step and Stop are converted to proper values

Trailing Start = how much profit the trade must have to be trailing-stopped. If there is not enough profit (if the Start is some positive value), trailing stop does not work for that trade.

This status thing is only a text object that is created when the EA is added to the chart, and then of course it can be modified. Again, it's just a text, I created this simple option one day, it's not a big deal.

No EA can work when the PC is down. EAs, Scripts and Indicators are controlled by MetaTrader, and when MetaTrader does not work, obviously no sub-programs (controlled by it) can work. The solution is to have a VPS server where to install MetaTrader and run it from there.

https://fxdreema.com/shared/TyxenJbDc

Is that happen on backtest? And what if you use different MT4 installation? I don't know... maybe some MT4 bug. iCustom function is used and there are no many things to do wrong with it in MQL4.
I noticed that weird things happen when the backtest starts. For example now if you create a trade in the "Init" event, it will be created but it's arrows can be put in wrong place.

I don't know really how they detect when EA is used. I can imagine that the Magic Number tells that, which is 0 for all manually created trades and orders, so when it is different than 0 it means that some EA created those trades/orders. In the EA you can choose to create trades/orders with Magic Number 0 (go to Options -> Project Options and set Magic Start Number to 0), but I guess there is something more than that, maybe some hidden information is sent with the trade/order which tells whether EA is used or not. Again, I don't know for sure.

No, use 0 by default. 1 is added inside the code. Calculations are over Candle ID + 1 candle, but for Candle ID candle. You can use "Indicator tester" to check any value.

In this example: https://fxdreema.com/shared/jqSylHObc
notice this: http://prntscr.com/3jb4t8
because of this Pentol Bakso does not give you correct signals.

Otherwise I still can't get this loaded/removed thing. Well, I'm not working in the exact same situation, but.... http://prntscr.com/3jb4y1
My indicators are loaded once, and to be honest, I don't know why and when it's possible for them to be loaded/removed multiple times

I can't get the same result. Can you create some project on the web version where this happens?

You can check if everything is fine. I used formulas that I found here: http://en.wikipedia.org/wiki/Pivot_point, otherwise there are many different kinds of pivot points out there.

I just added this to the web version: http://prntscr.com/3j4k79

What about some indicator like this one?: http://www.mql5.com/en/code/10990

It's also possible to calculate this stuff directly, for example in "Custom MQL4 code" block, but maybe it will be slower for backtest.

https://fxdreema.com/shared/V9Cg0DZzb

Block 2 is to be sure that for Buy trade the lowest price in the past is lower than the current price (where the trade will be opened). "Price fraction" here means something like 0.0012, which is not a price level like 1.2345 and not a (pips) value like 12.

Is it working anyway? And what MT is this, 4 or 5?

This is compile warning, not error. It's not wrong, only MQL4 does not like it.

I think I can't understand the problem with the keyboard

Is this the indicator? http://prntscr.com/3in5pn

These blocks are for indicators that looks like MA, where the price can cross the indicator line multiple times and the line does not disappear because of that. But I checked buffers for this one... I think something is wrong with them anyway.

Sorry, I can't suggest. This requires the use of DLL and named pipes and special EA that is used only for this. Maybe there are some EAs like this.

What, you wanted to delay trade with 3 pips? This is obviously a pending order, but I didn't expected someone to ask things like this

Results depend on the strategy itself. The problem comes when the strategy matches the disadvantages of the selected model (Every tick, Control points...). So you can have results that looks too good to be true, because the EA "hacked" the selected backtest model, it's like the model itself helps the EA to get these results. The chance for this to happen is greather when the data quality is not good, which means that higher timeframes are used... higher than what the EA needs. So what can I say... if you want, learn how these backtest models work, there is information about that somewhere in mql4.com. It's also possible for this result to be true, I'm not saying that it is wrong, but it will be better to investigate it more. Ticks Data Suite, Tickstory... there are some ways to do that.