Thanks. One step ahead. Found That. But new issue regarding my new Stop Loss Post..... THANKS!!!

I think Scripts work. No one complained lately, but not many use it, so...
You can try it anyway, for small experiments like this it's totally free.

Thanks that is good to know.

What, if you have buy trade to place it's stop at the lowest price since the trade was created? I think I'm missing something, because doing this is basically closing the trade right from the beginning or pushing SL further and further so it can't be reached (at least until the EA is removed).

If you want to place SL to the lowest value back in the history (for some time), then something like this: http://prntscr.com/4c34n8

You have <If some trade exists> on every tick. This will not create pending orders by itself, because there is no trade initially. But even if you have some trade, it will start creating unlimited number of pending orders, because the trade is running and on every tick you create a new pending order.

So what you have is an endless loop which (fortunately) cannot start, but if it ever starts...

Try it in the opposite way, with "No whatever exists". In this way you create trade/order when it does not exists. And then, after it is created successfully - it will not pass the "No..." check again.

Also you can check the number of trades/orders if something like this is needed. "No..." is checking if 1 exists.

There is also "on Trade" event, but if you can do everything under "on Tick" it will be better. Because the Trade event is fired ONCE when something happen, while "No..." block is basically a condition that does not depend on events.

I gave you examples 2 times already in email, what about them?

Hi
I recommends to you Tickstory litle. Dont use classic backtest on metatrader.
http://www.tickstory.com/
Its very good program and i use it for backtest on tick data.
Bye

I'm not sure about that. Normally the EA receives OnTick (and other) events for the currency where it is added on - when a tick comes for the current currency, OnTick() is executed.

In theory, if you really want to control all currencies the same way under the same EA, you should have some infinite cycle to detect tick events by all currencies. And this is not impossible, but when you have to work with some currency, all the others will wait. This is called "blocking".

Actually I don't know what will be the behaviour of such an EA, I never tried this. This is something that I had an idea to make, but it's still only an idea. I guess that if you have multiple EAs they does not wait for each other.

Thanks.

For MT5 make sure that you run fresh EA. There was a problem before, but I'm almost sure that I fixed it 🙂

Thx! I will check it out. However I can't even utilize the blocks to set the parameters. Like I said Newbie! lol

Thank, works like a charm!

Randomly...
This is how I made it initially, and it's the same way today. If you cross MA5 and MA20 with x>, the conditions are these:

MA5[0] > MA20[0] and MA5[1] < MA20[1]

where 0 and 1 are candle id's.
This works for indicators, because each indicator has 1 value per candle. It becomes a little bit weird when candle data is used:

Close[0] > MA[0] and Close[1] < MA[1]

Here it will be more correct if Close[1] is Open[0] instead. But in "Condition" is not. That's why I created 2 more blocks for price crossovers, which work in a little bit different way - they detect when the price crosses some value, but using data from the current tick and the previous tick.

I used the same variables here: https://fxdreema.com/shared/WqS5N7CV The result is not very profitable at least on my backtest :)))

Thos functions are automatically generated, I don't recommend to use them 🙂

__Ahaa, the problem is in the way blocks 20 and 24 are connected. This cause block 23 to run 2 times, once because of blocks 20 and again because of block 24[/quote:1wbqnl4k]

Gotch thx

In the beginning I created "Formula" block, few months later I added Constants and Variables. All these are global variables, so they are accessible everywhere in the EA. Only I don't recommend to modify Constants, they are designed to be constants.
So, when you define variables in Variables, or you create Formula block, some global variables will be added to the final project. I prefer Variables, not Formula block. And for some basic calculations with those Variables click on this "Variables" thing: http://prntscr.com/42j6wo

__1) This depends on the current conditions, the EA is not doing tricks for fun 🙂 I tested it, it was ok for me.
2) Mmmm check again
3) MetaTrader 4 is known for it's bad history data. Sometimes there are months and even years of missing data. You can go to delete some files (in "history" and "history/downloads") and download data again. It's not that this will fix all the problems, you will get holes of data in other places 🙂 This is well known problem for MetaTrader 4.
Or try Ticks Data Suite or Tickstory (use Google here).
4) You can't. These are trades that are closed when the finish date is reached. These are currently running trades at that time, they hold their profits and losses.[/quote:3e4417gr]

Thanx you.
I will try my best again 😏 to improve the EA, and make it as closer as possible like my will.
Many thanx for your help. 😉

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.

In the past all input parameters were accessible in .ex4 files, but now nothing can be read from there, or at least I don't know how. Well, copyright information can be read, but who cares.

I wrote some information in the window where indicators are organized, also look at the bottom half of this page to see what datatypes to use for parameters: https://fxdreema.com/documentation/proj ... indicators