Topics created by james

So everything works at least today... phew...

% of means percent of. 100% is 1:1. If the volume is 0.1 lots, then 100% of 0.1 lots will be 0.1 lots. 0.1% of 0.1 lots is..... something very small. So, with this option use values like 100, 150, 200, 300, 400... to increase or 80, 50, 25... to decrease the size of the volume.

Or if you use it with that Formula, use Fixed lots option. I have to add dynamic option...but other things are in my head, so I will try something else first.

Hello - me again! 🙂

Could I make a small feature request, please?

When you click the "Expert Properties" button in the strategy tester, up comes the optimisation variables you have enabled. Beside most variables inside each fxDreema block is a small tick-box to enable the variable to be visible and changeable inside "Expert Properties" in MT4.

Take a look at the following:

current properties box.jpg

requested properties box.jpg

It would save some typing and mouse work when testing to have the __-= Input parameters for block (n) ([/quote:o3skv1fh] bit removed. We should all know that this is an input parameter, and which block it is since __inp(n)[/quote:o3skv1fh] is visible in the column immediately to the left.

Just a thought to save my tired fingers!! 🙂

......
current properties box.jpg
requested properties box.jpg

Point format setting exists only to make the EA to work the same way on different brokers. Some brokers are 4-digits, others are 5-digits and normally when you are in 5-digits broker you have to enter value 10 times bigger than the value in 4-digits broker, and this is boring. Point format setting is there to tell the EA to work as if the broker uses that format, not the one that it is using. Set Point format to 0.0001 and the EA will work as if it work on a 4-digits broker even if the broker is 5-digits

I think I've worked out where I've been going wrong with this. Thank you for your help. 🙂

__Indicators has buffers. Every buffer has a value all the time, even when the indicator line (arrow, histogram) is not visible. In this moment the value of this buffer is 0 or 2147483647, it depends on how the indicator is programmed. 2147483647 is the biggest integer value and in MQL4 is presented by a constant called "EMPTY_VALUE". Not all custom indicators can be used in EA, it depends on the programmer as well. Some of the custom indicators may have values on their buffers, or value that does not change, and that's why I created this block "Levels tester...". Now, when you know what the buffers gives to the EA and when, it's a matter of conditions to create a proper trading signals.[/quote:2q6jx9hn]

Thank you now its clear for me

"New top in trend" and "New bottom in trend" does not use time in calculations. They are as accurate as any other candles calculations. These blocks checks back to see if for X candles the price moved for at least Y pips. And the third parameter is... if it's lower, more up/downs in price are allowed between the oldest and the newest candle.

I made those blocks to serve one of my ideas - to detect when the price breaks at a new top/bottom, and all the previous cadles are below/above that level. Maybe there are indicators to do that, I don't know. But for your question - time bomb and new top/bottom blocks are similar, but time bomb lives in a timeframe lower than the lowest possible for MT, and that's why it is innacurate in backtesting.

No, it's not because of the dll error. I have and idea what is it and it will be fixed for the next build.

OK. That's great. Thank you so much for checking this out. I'll get on with 041 now. 🙂

Ah ha! 🙂 That explains it! I'm so sorry to have troubled you. Thank you.

Yes, I added this new functionality, but it is for the web version at the moment. I will make new local build when bugs from the last update disappear 😕 They are almost gone.

I mentioned this earlier, but did you discover why build 039 displays this error upon launch? Build 037 didn't. I'm a little concerned about using 039 because of this.

......
fxdreema 039 launch error message.jpg

Hi

Yes. It seemed to come up, but I didn't feel confident about using it so reverted to the older version again. 🙂

I'm really sorry about this. I think I haven't explained myself well enough.

I actually did as you suggested; I inserted the statement into the Value (numeric) field, but that didn't work. 🙂

Oops, I found a problem with reading the last available build, and unfortunately the problem is in the .exe, not on the server. I will create a new build now (039).

It was interesting to me when someone will ask for these blocks 🙂 MT5 actually natively supports this event. I have plan to make them.

Superb!

Any idea on when a new local version download will be available with these?

Oops! Sorry! My mistake. You are, as always, quite correct. I didn't do Projects -> New project (choose MQL5). I'm too used to just accepting the default! 😳

https://fxdreema.com/shared/TXXnF2sJb

I doubled stack size for the web version. This is a simple MQL code at the top of the file that looks like this:

#property stacksize 2097152

It is measured in bytes. To be honest, I don't know what it means, how it works and how big it should be 🙂

On the update that I'm preparing there will be many changes in the code of fxDreema, so this problem may disappear.... and other appear 😄