@miro1360 @roar thank you very much

Hi

I don´t know if as a string variable it will work or not but remind what @fxDreema has explained in the forum about this: if there is no tick coming at that time, it will not be posible to meet the condition time.

@fxDreema suggested to use a period of time to get what you want such as if time > 23:30 --> Close positions using the condition block or a time filter block.

0_1525208656714_807b1bca-22a9-4229-90e7-51908b093e3d-image.png

Should work.

I saw that i had to enable popups from fxdreema. I didn't see it before.

Your "y" variable doesn't change at any point.
Also, alone blocks will not work, there must always be a connection.

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...

In the last picture are you sure you want blocks 5, 6 and 7 to be below the Buy now block? I hope you know that Buy now doesn't run on every tick, so 5 also does't.

Anyway, to check whether some block passes or not, simply connect say Draw Arrow after that block and look at the chart for arrows.

I think that the EA you made is working. I might also want to try this block "Indicator moves within limits". Or maybe this concept: https://fxdreema.com/demo/mt4-wait-crossovers

The code in question (where the extra , appears) is from 0_1525114137436_cf527b4b-5793-4722-b0d6-40fe1618072d-image.png
I will check it, but I think it's better to add the indicator in the system and work with it via "Indicators (My Indicators)"

There is no "after", even the "Indicator moves within limits" block looks at the past and uses the history candles to check these values. So all blocks are normally working in the present moment with history data. And it looks that you wrote that you want that.

@josecortesllobat said in EA from Examples:

connect the block #7 to the yellow output of block #3

I am not using the yellow output of a cross over condition.

@josecortesllobat Hi!
I think block #3 is a cross-block. But yeah, its best to make separate flows for buy and sell in this case.

use Bucket of Trades ...

https://fxdreema.com/shared/NtGNkJy9e

I think it refers to the different indicator "buffers".
You see, an indicator can have all kinds of information to offer,
for example, the default MACD indi can give you the main line value, and also the signal line value.

I found where the problem originates and I think I fixed it, but I'm a little bit afraid to upload the new changes that I have (there are other changes as well, not only this), because the last time I broke few people's projects. So after that I decided to first work on the website locally (my local working copy of the website that I use often) and when everything works fine for few days, to upload.

Error messages? Another browser works? What exactly means "does not save"?

I don't know how the indicators works, but I don't care, because I know how indicators are used by the EA in general. The normal way is to read the data from their output buffers. If there is no data there and the indicator only draws objects on the chart, then we can only work with these objects. So it depends on how the indicator works 🙂

@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.

When the signal is no longer true? But what kind of signal is this?

If you are talking about the comment, the attribute that every order has, I'm afraid that you can't change it. Only in OrderSend() we can set that "comment" parameter (https://docs.mql4.com/trading/ordersend). For partial close OrderClose() is used, but as you can see, there is no "comment" parameter there - https://docs.mql4.com/trading/orderclose

I don't know. I never used copiers and I don't know how they work 🙂

formula:

candle close (ID 1) - candle open (ID 0) remember to use daily timeframe in the formula

then condition: formula result > yourGap