Posts made by fxDreema

They worked for this transition for months, I tried this new MT4 months ago and I have waited for it to be launched. Now there are some bugs, I understand that (also because this happens to me when I do bigger update), and I like that new MT4 because it is faster in backtests, MQL4 has now all the positives from MQL5 and MT4 still allows multiple trades (not positions). In short, it looks to me that MT4 build 600 is the beginning of MT6. I will like it if they kill their MT5 completely and call MetaTrader 4 just MetaTrader. Now that MT4 has the positives from MT5 and does not suffer from the "positions" limitation in MT5, I think that people will prefer MT4 even more

Well, in a matter of fact I keep prices low mainly because of this reason - I don't feel that my software is top quality. It's not that it's bad, but sometimes when I do updates, bugs appear. And what are $19 in the forex world - few spreads that every trader with real account will give away to his broker anyway. It can be used also for free, actually there is a way to easily workaround all limits by making shared copy of the project and work on it (web version only). Interesting fact is that there are many newly registered people that decide to subscribe within hours or minutes, I don't know why. I think it's best if a person play with the program for some weeks until it gets the idea, and then to subscribe if he wants, because if he is a total beginner he will not be able to do something big anyway.

These warnings you mentioned are not fatal, they appeared with the new MQL4 rules. But I found 2-3 fatal ones in few blocks and I fixed them.

With some variable for example. There are special blocks in group Flags that are to be used in this way - to store some value in one block and then check it in another. Or this Variables thinng on the right just above the Actions History panel. But these methods use temporary variables and if you restart the EA that information will be gone. If this is not a problem for you - use it. Otherwise for persistent memory, hmm, maybe I will start to recommend these Global Variables more: http://fxdreema.com/documentation/proje ... metatrader

Ahaaa, it happens when "" are used! Ok, I think it's fixed now for the web version.

And it works with FractalChannel too: http://fxdreema.com/shared/22i1CaPvb

I'm now on a different machine and I have no ""FractalChannel" in it, but I tried with Bollinger Bandls, which is very similar, and it seems to be working: http://fxdreema.com/shared/NFbXlMxOb If I have Buy, it's SL goes up only when lower BB goes up.

Interesting, what do you input to them?

I think this is because MA also goes up/down when the price goes up/down and the crossover extends itself. Maybe Once per bar can help? Or maybe some tolerance.

Trailing stop? Maybe checking if the current SL level is below/above the one that is to be set. But I think that trailing stop block can be used for this, well, 2 of them

Ah, this is because the compare sigh in block 1, it's wrong. But otherwise I found that the returned value of tick 1 is the same as tick 0. Try with tick 0 and 2, or even bigger difference.

When you use "Draw horizontal line" block it has an option to choose at what price level to draw that line, and by default it is Bid.
Now the problem with your project is that the initial value of that Formula variable is 0 and block 7 is true from the beginning

No. Normally there is no way to set previous tick for price, but I added a function to collect this data, which also makes the EA to run a bit slower on backtest It's not impossible in theory, but is it needed?

I have some arrows out of this project with MA shift 0

At what level you place that horizontal line - this one. Bid, I guess.

What is this in those conditions... you compare value like 20 with price value, and with "==".
Size in pips returns value like 20 (for 20 pips). I think you should use the Level option. And when comparing two price levels, don't use "==", use something that contains "<" or ">" instead.

Objects can be used without their name, here is an example: http://fxdreema.com/demo/mt4-object-in-loop
To work with the last found object set Not more than... in the first block to 1.
But I will suggest to save that level in a variable and then check it's value. Well, a horizontal line is something that stays there even if the EA is restarted.

I think in your project you don't need to set MA shift to 1

Crossover is to have Close[0] below MA3[0] and Close[1] above MA3[1]. This is what I got: http://prntscr.com/2rrx6g
On 17 jan Close is deep below MA3, but Close of 16 jan is also below. At least this is the algo that is used now, which is maybe not "correct" in every situation. If for example we have to compare Close[0] with MA[0] and Open[0] with MA[0], maybe another wrong situations will appear. There is another possible way - to compare the current Bid with the current MA and the previous Bid with the current MA, and this will give us 1-time signals... I think this is for a block like "Price cross indicator".
Obviously there are number of ways to do something. What is the right way to detect crossover in your opinion?

I have personal life and I am very free spirit, so I don't like to be slave for anyone. Some people do it better when they are pushed, but I'm not one of these. And if you search for other similar products, I really really doubt that you can find something that can do more, is cheaper, and it has better support. I will send all your money back as soon as possible... if you want to.

Can you try with the code I posted before?

iLow(Symbol(), 0, iBarShift(Symbol(), 0, OrderOpenTime()))
```#
here Symbol() means the current symbol, 0 means the current timeframe. iLow returns Low of the candle with ID that is get from iBarShift() function. OrderOpenTime() is the open time of the currently loaded trade, so I guess "For each Trade" block should be used to load trades.

I even doubt if it's a good idea for me to add such a parameters. I can probably make it possible to get candle data not only from candle ID, but also from candle Time, but then you still need to get the trade's open time.

I think that you are trying to do something in the hard way. Whan do you want to do with these candle levels, isn't it ok to just set SL or TP or pending orders at these levels when they still belongs to the current candle (0)?

I think this is too complex and specific to be made with available blocks. Maybe some specific block with custom code, in theory it's not impossible, but it will not be elegant to do things like this with blocks because there are many small calculations and conditions.