Posts made by fxDreema

I can see that you are using MACD now, and this indicator has values very very close to 0. But I don't understand what you want to detect actually. At least I can't see how for 500 candles MACD can be above 0 or below 0 only, this indicator goes in the other direction every few candles. The other thing is that this indicator is an oscillator, so the exact value 0 does not mean something very special to it. If there is an indicator that can have values -1, 0 or 1 it is a different story. But I don't understand why you want to check if MACD had a value 0 (exact 0) in it's last 500 candles, what is that mean? And is it possible for MACD to have value 0 actually, I think (not sure) that this indicator is either positive or negative, so it's probably never 0 by nature and to check if in the last 500 candles it is !=0 will probably give you always the answer Yes. So... do you want to detect MACD crossover with 0 or something else?

I just uploaded the new update, but I worked for it in the last month and there are some invisible changes into the database structure. There is almost nothing new that anyone can spot, but I want to warn you that problems can appear. I don't know what problems, after all I hope that everything will be fine... but just in case.

If someone finds something that does not work as before, please, share that problem with me.

Even if someone lose his project or part of it - there is a backup, but share that with me as well.

Ah... I want to also apologize that fxdreema.com didn't worked last few hours... or more (i'm not sure how long). There was a problem with the company that hosts my domains, they are on different hosting than the website itself. Otherwise the website is working perfect in it's new hosting place (since May, 2013).

No, don't create 100 blocks only for this. As a code this is something relatively simple, and there is a block "Free loop..." that makes the next blocks to execute N times.... but it's not a good idea to try it because there is no way to break the cycle when needed (and if you check all 100 candles on every tick, even if the first one failed, this will eat the speed of the EA). But this block "Indicator moves within limits"... what if you put 2 of it, one for the positive side (indicator is above 0, lower level 0) and one for the negative side (indicator is below 0, higher level 0). I didn't tried it, but it sounds fine. Otherwise I can make a block to do exactly what you want... but a little bit later, because now I have something to do

mmmm what?

What about "Indicator moves within limits" block?

Maybe I will recommend you to use Condition block and "Adjust" field to detect indicators rise and fall It's more direct way to do it The idea is: if indicator[new candle] > indicator[old candle] + some value => then indicator is rising with at least "some value" between those two candles.

Indicator rise = indicator moves from lower point to higher point. It is lower in some old candle in the past and it's higher now.
Indicators like MA have values like 1.2345... price values. The difference between two points of MA is how much? You use value of 2, why?
I will remind you that this block had "pips rise" option, but not "value rise" option. Do you understand the difference? In other words, do you understand the difference between ADX and MA? ADX has values between 0 and 100 and point distances are measured in.... I like the word "apples", MA has price values and you can measure the distance between two points in "apples" again (like 0.0002 or 0.0013...) or in "pips" (where 0.0002 is written as 2, but means 0.0002).

By the way it's better to connect 2 blocks one after another instead of using "AND".

There is no limit, I have seen projects with more than 1000 blocks... but the project becomes too heavy for the browser, and for the mind as well. I'm testing the speed of EA generation with 400 blocks, but I don't recommend to have such a big number of blocks. If the EA contains 50 blocks, it's maybe time to optimize it. Sometimes I need to add some feature to make things simpler, but I have to know what is the idea.
In other hand it's pointless to have big EAs, because EA is basically to trade by signals, and signals are received from indicators. Well, fxDreema cannot build indicators, but this is the idea

This may give you some idea: http://fxdreema.com/shared/mvDMmzTK
When a new sell trade is opened (detected with block 3), we load every buy trade (well, it is only one, with block 7) and modify it's SL with the TP attribute of the trade that caused the "on Trade" event.

This is indicator And yes... if there is an indicator to do that, it's maybe the better way. After all indicators are made to do different price calculations... candles... numbers... and to give the EA signals when to trade.

I think it's possible, I wanted to be able to do that these days... I have to see how to make this.

Buy now -> Sell now

Click on "Group and Market to use" and write down the desired market (symbol).
Notice that this cannot be backtested in MT4, as the backtester does not work with more than one currency pair (the current one).

http://fxdreema.com/shared/WcpGkLNdb

Oh, try with Candle Close [0] instead of Ask price. Crossover here means that two lines are crossed, but Ask itself is a point. Candle Close [0] works as a line, because Candle Close [1] is also used in that calculation.

I mean, to have crossover you have to know where the price was in the past and where it is now. If in the past it was below certain line and now it is above - then you have crossover above (from below). But Ask price itself does not have nothing in the past.

Well, I can do something to workaround this, to collect ticks from the past and use the previous tick, then I think it has a chance to work... but it's better if you do it with Candle Close [0], because Candle Close [1] point (which is used to describe the past) is at a good distance from Candle Close [1] and everything is fine

This is nothing, SymbolInfoInteger() obviously returns integer (int) as it's name says, but sometimes there are warnigs like this (and I don't know why). Probably the correct datatype of this variable "t" should be "datetime", but "datetime" is just a different name of "int", so these warnings are just warnings.... and they probably exists in build 044... I'm not sure.

I remember this bug, but I didn't expected that it exists in the very last build which is more than month old... It is only in MT5 actually.
Well, right now I'm working for the new update, which is... I'm rewriting my own old messy code... and I will be able to create a new build later, but I tested build 043 and it seems that it does not have that bug. The problem with 043 is that block's list is not fully visible and some of the blocks on the bottom are not accessible, but they are not the most important, so I can suggest build 043 now: http://fxdreema.com/public/_misc/fxdree ... ld_043.exe

To test any price level from any indicator, candle, and most of the things inside "Condition" block... basically any numeric values, use "Levels tester" block, as it can show you values in realtime.

I guess this is the local version. Build?

Why do you have "Price level 2" in blocks on the right? There are objects with 2 or 3 coordinates (price levels) - trendlines, sqares - but the horizontal line has only 1.

Nevermind, to understand when some block passes, connect "Draw arrow" to it's output and you will see the moments where it passes on the chart in form of clouds with arrows.

There is a function named Alert() in MQL4. Here is how it works:

Alert("some text here");

or...

Alert("some text here"+", and some other text here");

or...

Alert(Symbol());

or...

Alert("my current symbol is: "+Symbol());

or...

Alert(""+Symbol()+"");

So, + is like glue, and you can put as many things as you want to display, one after another with + in between. Strings (texts) are always with " in the beginning and " in the end. Digits are not.

Alert(12345+"some text here");

will alert this: 12345some text here

Text in Condition outputs what is in the field, but it automatically puts " in the beginning and " at the end of it. So, if you write just Symbol() it will become...

Alert("Symbol()");

and this will alert: Symbol()

but Symbol() is a function and at the end it must be executed as such, something like

Alert(Symbol());

but because the generator puts " and ", then we need to do some thick until we have this:

Alert(""+Symbol()+"");

and this will output: EURUSD