Posts made by fxDreema

I guess it's ID 1880. After block 3 you can place "Comment on chart" and put it there... if this is what you ask for.

I think I fixed it. But when you export .mq4 file, it also contains fxDreema project data, I even plan to remove the option to export .xml file.

......
Test-XML-File.xml

It's not normal, it must be more than 0 bytes. Can you give more details?

Now?

Is it working now?

I have made some update, but with a little mistake. If you try it now, is it working?

Oops... I think I fixed that. is your "Stops level" for that symbol 20?

This creates trades on my backtester. Do you have error messages?

EA name or EA id?

Ok, now "Indicator moves within limits" must be working in the way you expect

Now that I'm looking at this block "Indicator moves within limits" I realize that maybe this is how it should be, but at the moment I think it uses the same value for the upper and lower limit. But it's not hard for me to fix it, I even found a little possible problem in it, so I will check it.

For the other question, what parameter do you expect to be included to "Indicator rise"? How it should be named and what it shoud do actually?
Now what this block do is to compare the values between each couple of candles in the past (candle X vs candle X-1) and if the value of candle X is lower than the value of candle X-1 - the block fails and it does not pass. Knowing this, what it should be added to this algorythm?

I thought you want to check if Close is above MA, but for every candle - Close[0]>MA[0] and Close[1]>MA[1] and Close[2]>MA[2]... which is still possible, but with multiple blocks... It's not beautiful I like that concept

Number 1 - what if you use indicator with bigger period. I think you want to filter those situations where the price goes back and returns back quickly.

No... but how do I know if someone uses the local version or the web...

Well, I also found another bug, so build 048 is expected soon, but I also started to reorganize categories in "Condition" and adding some pictures inside, and I'm not finished with this.

And I am very picky when it comes to new features, because every line of code that I write will make things good or bad in the future

So you are thinking about the interaction between two indicators in time (candle close is also indicator). This is not for "Condition", because in "Condition" you compare 2 values, but it's not possible to do that for X candles in the same block. It's maybe possible to extend the "Condition" block to work with additional candles, but this is new concept right now and I'm not sure how good is it and how to do it. Otherwise in a block this can be done easily - we put 2 indicators there, and do something with them... but I still don't understand all the things, or al teast I don't know how to name such a blocks. But if you have an idea how to name them...?

Yes, and I think that is excellent to do something, then to broke it and fix it... and again, if that is not enough

I'm not sure that I understand, but I can discuss the example.

First, you detect when a trade is closed, note that this will cause the next block to be executed once.

Then you have a loop, which normally loads all trades one after another and does the next things for each one of them. I guess you have to put value "1" for Not more than N trades parameter.

Then you have "Pips away" block, and in this case there is no way for this block to react, because if it is executed once when the trade is created, it still has no profit. An no, this block does not work by itself somewhere in parallel universe, but it does what it is supposed to do when it is executed (and this is true for all blocks).

The last block - well, if the project is like it is now, it can probably close part of the volume for another trade that is running (not the one that is created). That's because now the loop (block 3) works for all trades created by this EA.

If you want to close part of the volume when certain profit is reached, use that loop under "on Tick", and place "(in loop) Once per trade/order" before block 5 to not execute it more than once for a trade.

Fixed

What "Condition" block do - it compares 2 values (operands) and if the comparison is true, it passes.

What Indicator is visible for the current candle and for the additional candle means - inside the block we check if the indicator is visible for the current candle (3 conditions inside - different than -EMPTY_VALUE, different than 0 and different than EMPTY_VALUE), then repeat that for all the additional candles.

In "Condition" you want to get the number of occurrences where the indicator is visible in once-per-bar fashion (because in Condition for each operand you should have simple value), and with some options if possible... (more at the beginning, more at the end, and who knows what else) so you can compare that number with the other operand. But unfortunately I have no plan to work for that right now, because the "Condition" block is not prepared for things like this. I have plan to add drop-down selector for every indicator, where we will be able to choose << Current value | Last positive value | Last negative value | Candle ID of the last visible value .... >> things like this, as universal as possible. So, there is a chance for "For how many candles that indicator was visible in the last X candles"... but I think the chance is very little Why? Because after all this is job for the indicators themselves - yes, indicators are meant to give proper signals for the EA, not to be cracked into working in a way that they are not supposed to work, and if the indicator needs to draw simple arrow when for X candles... whatever happened... then if this procedure is too unique, I prefer to skip it and redirect people to some of the well known forums where they can find enthusiasts who can eventually put some simple code inside some indicator in order to work the way that is needed

Isn't that specific to that indicator? I'm trying to create universal blocks that works in most common situation, but this thing... how can I explain it? If in the last X bars if buffer 1 is !=0 Y more times than buffer 2 is !=0 - then pass...

I have no problems loading projects, everything looks fine here

It's so good that I don't work for Boeing, so many lives are saved Get build 047: http://fxdreema.com/desktop