It works now. Thank you for reporting this

Martingale is to double the lot size on loss. Loss means that the last closed trade is not profitable and it's also closed.

Some people wanted to do it in the "wrong" way - do calculate the lot size from the newest already running trade for example. So the block first searches for such trade and only if it doesn't exists it takes the lot size from the last closed trade.

For Martingale there is no memory where the last lot size is stored. It depends on the lot size of the last trade. If that trade was loss - it doubles that value, otherwise the value is reset to the initial. And of course it depends, because there are many options, but I'm talking for the default Martingale settings.

So I think that you have one trade still running when the new one is created and it works with its lot size. If you want to separate things, try with different Group numbers.

Yes

Well, if this does the job for you, why not. Maybe it's not that useless as I think 🙂 The thing to remember is that it always checks values from 2 candles, even if the value of 'cross width' is 1000

I think that "Delete" worked before, who knows what happened, but I will check.
I think I actually noticed once that something wrong is going on when there is only 1 indicator in the list 🙂

Whatever problems you have, in the way you explain them to me I can't say much, because there can be many reasons. It's different if you show me a project and tell me "I expect this to work this way, but it does something else".

And you are showing me some project, but what is the problem in it? You say "Also cant get my closing rule for pending orders or trades to work", but what is that rule? Now there are some blocks and they probably do some logic that can be right for someone else, but not for you. Why? What do you expect to happen and doesn't happen?

https://fxdreema.com/examples/
https://fxdreema.com/help/

There is a block called "Once per bar" and this block can pass 1 time per bar. Put it before or after the condition and the result will be different. There is no such thing as "on close of the bar", but if you have "Once per bar" on top level, it will detect when a new bar is created, it will pass on the first tick of the new bar. In "Condition" you can always set Candle ID to 1, 2, 3... or anything else to work with the previous candles.

This is because currently the desktop version is few months old and it doesn't understand the data stored in the .mq4 file, because it's newer version

I will check

Thanks , no error messages 🙂

Thank you again :)))
I'll try it out but anyway I'm not sure if for my ea this would be suitable. I have to think it over again :))
Thank you very much really... 🙂
Have a nice day!

Copy of the project data is automatically embedded at the end of all .mq4/.mq5 files that you create (it is compressed, that's why it looks weird), so you have the actual code + fxDreema project data in the same file. Imagine that those .xml files are now .mq4 and .mq5 files.

I change things sometimes and I even change the way that project data looks like. Old project data eventually becomes in "wrong" format for the new version of fxDreema, but I have functions that convert it to the newest version. Now the local version generates old version of that data and the web version can work with it, but the opposite is not true. If you try to import .mq4 file from the web version into the local versions, it will fail, because the local version is not aware of the new rules.

Would be great to have a free formula block where we can write some mql4 code

area for some lines of free code (hints apprecheated for the existing variables / constants / MQL4 keywords)
last line must be an assignment like
[ResultVariable = ] some free code.

the User must define the Name of the ResultVariable

This was another problem in For each Trade 🙂 I expected that "strict" mode is responsible only for the syntax, but it looks that it does something while running.

Just want to add that after revert back and thing or two and multiple time of restarting, it is now working as it should.

Hello,

I replaced mql.exe found in the following location: C:\Program Files (x86)\fxDreema\Data

The link for the mql.exe file can be found here: http://files.metaquotes.net/metaquotes. ... t5/mql.exe

That fixed the problem thank you.

Great that works for me

Yes... it come back to work now!

Thanks!

Forgot to reply, thanks, my bad.