Topics created by james

Sorry. Yes, it was for the local version. And your helpful reply fixed matters.

Thank you. 🙂

James.

Hopefully, but the chance is that this parameter does not work at all, because the broker itself does not work with it 🙂 I think I read somewhere that this is normal for ECN brokers.
Someone was asking the same question and I did some tests with OrderSend() and different values for it's slippage parameter - I still got trades with slippage, no matter what value for slippage I used, and I tried values like 0, 1, 10, 100, 1000 and negative values. I don't remember which broker I used for this.
Don't rely on this parameter too much 🙂

Don't know what ZB is either!

I just think that you could do what the wizard does soooo much better! And make money from your labours! 🙂

Anyway, hey ho!

With custom code only, not possible in Condition.

Yes. Thanks, I realised I could do this in a global variable, but I suppose I'd also like to have it in a safer non-volatile format! 🙂

For now I'll keep to the global variable, and look forward to a new block sometime!

🙂

This is the idea, but if you want to check if it's working correctly, place some Alert message block after that one

My apologies. I used the daily candle to try to keep things easy, but all I did was to confuse! Sorry.

I'm trying to achieve this:
__
*

when a new bar opens, send the time of the closure of the previous bar to a variable place this value into a once per day block, so that the blocks attached to it can only execute within a 15 minute interval
[/list:u:14101pd8]
[/quote:14101pd8]
With your kind help, I've got as far as placing the time of the closure of the previous bar into a variable correctly.

The next bit is eluding me. I just can't work it out! 🙂

It seems to me that I need to come up with a magic way of extracting from the unix time, a value in "hh:mm" format, place it in a new variable, and drop this into the "from" and "to" fields of the once per day block. Sadly, my magic isn't strong enough (indeed, its pretty weak!) to come up with the method. I appreciate I may need to use a Custom MQL4 Code block along the way to achieve this.

Any suggestions would be most welcome!

Thanks again,

James.

Hi

Yes. That seems to have cured it!

James
🙂

From some months the native MQL4 function OrderSend() handles instant and market executions by itself. I don't expect problems, or at least not after all the work is done on their side 🙂

That's it fixed! Thank you! 🙂

Hello again! 🙂

Thanks for your speedy response and quick fixing. Sorry for my delayed thanks! All seems OK now.

James.

🙂

Er... sorry. I'm back!

When I make an entry in the text are in block descriptions, this is not saved:

1 - create a "Pass" block
2 - edit title to "testing"
3 - click "Save" and/or "Export to..."
4 - close fxDreema local
5 - open it again

...and the title of the block has returned to "Pass"!

Help!

🙂

I found the problem, it will be fixed in the next build 🙂

They show how to generate report at the end of the backtest, but in the middle of the backtest how to make MT4 to show you that there was a withdraw, to make changes to the Balance/Equity chart, to make functions like AccountBalance() and AccountEquity() to return correct values. I don't know, if I have to do tricks with MQL4 and MQL5, I will rather program a whole new backtester. But this is something bih and I already think and work for different kind of project 🙂

OK. Will look forward to it! 🙂

I think I now have this - after much confusion on my part! Sorry.

So, for the benefit of anyone else doing backtesting, and searching this forum, this is what I've done:

Using Alpari, and US500 index (S&P500)
*
FxDreema: Project options => point format rules: 0.01 = 1
MT4 tester: set the "Spread" value to 85
[/list:u:2ps5mesl]

Running a short test over a week or so I've found that Alpari's average spread on US500 is 0.85 pips (85 points) - remember, its a 2 point format in use on this index on this broker. Therefore, the "Spread" value to use in MT4 tester is 85, although the result of ask()-bid() (which you can see by making a "Comment on Chart" block, with "Market properties => spread size" options) will say 0.85.

Hope this is helpful for somebody! And if I've gone wrong, please tell me!
🙂

Sorry. Didn't mean to confuse you. Anyway, all my sentiments were well meant! 🙂

Ah! Its the project expiration date! Sorry! The terminology, "The trial version has been expired!" had me confused and thinking it was something internal to fxDreema. Acutally the project expiration date is something I haven't as yet used anyway.

Thanks for the help - as always!

🙂

Hey! Cursor back again! Must have been in the re-uploaded local v067. Thanks again.
🙂

Yes, sticky problem fixed! Thank you!
🙂