Posts made by fxDreema

The test ends by itself or it hangs?

If something hangs, then the reason is most likely infinite loop somewhere. But I don't know why this can happen in MT4 just like that...

For each Pending Order -> slide order

But why... I don't think that slippage happens on pending orders, why don't you just place them on the correct price from the first time

Signal? Variable? I'm confused, but if you want to check a Variable, then in Condition put that Variable... let's say in Value->Numeric and compare it with something similar. Value->Boolean also works.

Well, this thing is... I can't say impossible, but it will be ugly. The logic itself is really easy - "for" loop, checking values in it and breaking the loop when the crossover is detected. There is a block to start loop in fxDreema, but then you can't break it. I would say that the whole idea is much better to be made as a custom indicator.

It looks correct. I made this to check the block, I think that it's working as expected https://fxdreema.com/shared/rpdSx31Oc

There is no block that can do this directly, although I believe I got the question few weeks ago and now I think I should add this somewhere. Here is something that can be used right now (contains 3 Variables): https://fxdreema.com/shared/87wpSB4Jb

What "don't work" means exactly?

I added something new there. You can check if it works.

Try this - http://prntscr.com/brpse2
"Original" is the real number of digits. "Customized" is the changed number because of the "Point format rules" settings.

As a MQL4 code, I think it was something like MarketInfo(Symbol(), MODE_DIGITS)

Ok, but take the natural ZigZag indicator and try to do something with it in the EA. It's useless in this form

__I was unaware that you needed to create a bucket of trades. I thought that as soon as you assigned any bucket of trades block that it was assigning the bucket according to the group # you would use.[/quote:2m1vnv8t]

The idea of "Bucket" blocks is to select multiple trades/orders, so then you can get calculated values such as their total profit. I don't use the word "group" , because this word is already taken for the Group #. What a "Bucket" block do is to find the trades (considering it's filter settings) and put their ticket numbers in an array. Then in "Condition" what happens is to read that array, get these ticket numbers, load those trades again, take theirs... let's say profits, add them and give you the total profit.

Also, I wanted to be able to load multiple Buckets at once, so you can compare the total profit for sells vs total profits for buys for example. But I decided that it's better to differentiate different buckets by color, not by name or number. That's why you can see these colors - Gray, Blue, Green, Red and whatever... they are only few.

http://prntscr.com/brpb6d - this should be only used under "on Trade".

I think you need to understand this concept, because the way you connected this condition does not look right: https://fxdreema.com/demo/mt4-wrong-closing-rule

I would try to do everything under "on Tick" and only if needed I would use "on Trade" for something. Because "on Tick" is more... reliable, let's say. So, under "on Tick" you can for example detect if there are no trades at all at any moment, which could be the moment to create new orders. You can also check the exact amount of trades, orders or both. There are also blocks like "Close trades" and "Delete pending orders"

In Example 2 those "Bucket of.." blocks are working pretty much like "Pass". What these blocks do is to take a look at the existing trades and prepare some array that can be used later. There is no visible result from them, but if you run them, they can pass. And this is what happens - they run on every tick and because trades exists, they pass. Why they run on every tick... because why not, these are the rules for blocks who are on top level When they pass... you make even more trades

miro1360, thank you for replying to some of the questions

Indicator arrows are the object representation of indicator's buffers. It can be enough to use "Condition" and to put inside: The Indicator > 0. And before or after this block, I guess, "Once per bar"

Interesting, what I mean by this... I wonder if this is a bug or something intentional.

I can see in your projects, but you have only 2 and there is no time filter block in them. So yes, provide more information

Yes, in fxDreema you define the size of one pip. In these settings you can say to the EA to convert certain points format to pips. I remember that back then in MetaTrader they never used "pips" as a term, they used the word "points". So, by "points" I mean the real difference between two prices, like these 500 points in 5 digit brokers. By "pips" I imagine 0.0001 in most USD currency pairs, no matter if the broker is 4 or 5 digit.

http://www.investopedia.com/terms/p/pip.asp

This is true. Here is something I wrote before - post/11013

I don't have problems with this: https://fxdreema.com/shared/4IlVstyzc
Give me EA that contains 2-3 blocks, only what is needed for me to see the problem. I can see your project, but... too big for me to investigate. I just need small project that will show the problem when I put it to my tester. When I have this, I will see the problem and I will fix the problem