Well, as you probably know, lines are normally drawn by indicators. And their lines are actually a little bit different kind of lines. If you try the "Trace" block, it draws a line, but that line is made out of multiple trend-lines, multiple objects. Compared to that, Moving Average draws a line that does not appear on the list of objects. So the best is to make a custom indicator. EAs are primarily designed to read indicators data and put trades and orders here and there.

@drayzen If the blocks are connected one after another, these numbers mean nothing. In this case if a block passes, the one after that is executed and so on... but the numbers are meaningless in this case. Numbers are only important if after a block there are 2 or more paths to take.

No trade -> Buy now? Sounds to me like you want to have only 1 trade at a time...

I think there is a bug and I will fix it

EA generated with fxDreema doesn't care too much what the broker is. The idea is that the EA decides how many digits to use and this is done with these settings:
0_1526500067267_685eb7b2-6e83-4319-b200-80095408b36f-image.png

Look for error messages. Be sure that you run the newly generated EA files. Test simple projects, such as "No trade -> Buy now".

Inputs are global variables... in fxDreema I call them Constants - https://fxdreema.com/tutorial/builder/constants-and-variables

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.

I don't know, this version is so old and I don't remember its error messages. But it is a portable application, so whatever happens, it is local. This version only connects to fxdreema.com when logging in and after that it is completely offline.

somewhere must be logic error 😄 try to find it with simplification of EA 🙂

Its still working. But you get a white screen first for 1-2 min. After that it should be OK

Thank you 🙂

@miro1360

I have figured it out now, I just didn't know that you can put the indicator simply onto the backtesting chart without putting it into the EA itself.

in that case use 2D array, mql support sorting by first dimension ... and other dimension will be reference for another string array which will be holding names of variables
here:

https://fxdreema.com/shared/HSKz4cwHc

0_1526113788869_67f213c5-575e-44bb-bc47-b2175a668362-image.png
0_1526113917119_8aeefe8a-c4ff-4dcf-8890-51a627ff04eb-image.png

0_1526113715076_2de76445-e818-41fe-9fcd-4cfc0d89b992-image.png

@ciclon

Those values will be a couple of bars back always since the indicator works that way , try to use indicator visible block and check for a range of candles like 10 or so , then it should be able to find them

Hi @jtex555 ,
I actually just used the Indicator falls within limits block for the first time and it sounds like what you're after.
https://fxdreema.com/shared/SwJ2mrNPc
In this example the Condition block is for C0 and the Indicator falls within limits is for C1+n.
You can even specify a number of candles in the range that can be out of your limits.

That did the job! Probably the most fast solution i have ever received 😉 Thank you. On a sidenote i had to change a little bit regarding candle ID for it to work.. Instead of find candle by candle ID i had to change it to timestamp as well; https://fxdreema.com/shared/zTDnSF0kc

Problem solved!

Thank you.

@nanana

Take a look at the @roar project. The variable "barcount" has been placed in a wrong place (adjust field) in your project. This is not correct.

0_1525877950298_d6a22c01-3eaf-4905-8af1-ec4a23f20caa-image.png