It looks that this error is produced by the indicator. Make sure that all parameters are right and in order, but if they are... I don't know, indicator bug

Ok, but this is not for the lot size, this is for the prices - SL, TP... price distances. There is no such thing for lot sizes, but it's a good idea and I will write it into my To Do 🙂

Fixed!

So happy i finally managed to get it to work on Pepperstone also. The problem had deffinately to do with TP as all variables that included TP, including "close on TP", "pips/percentage from TP" etc etc did not work.

Right now it scans for profitable trades only (greater than 0.1 deposited currency) Then it scans the distance away from opening price

https://fxdreema.com/shared/oXZRApxO

Distance from opening price works while everything related to TP or SL does not it seems..

Sorry. Yes, it was for the local version. And your helpful reply fixed matters.

Thank you. 🙂

James.

Many thanks! The moving average insight helped. I managed to solve it!

MA set to Candle High, Period 1, Cross Width 1. This validates it must have crossed under at some point and at least 1 candle wasn't touching the MA.

No problem. Wasn't expecting a 1 month bonus as it is still an awesome product to me 😄 . Thank you.

Hopefully this problem can be resolved after you finish the rewrite process.

True, here is how it looks for me
http://i.imgur.com/LDZaZeq.png

Only if you have block that is not connected to another does not work. Block that is alone.

http://prntscr.com/5xoi62
This is what I have... because I used M5 my pending orders have parameters very close to the current price, but otherwise they are placed where trades are placed in the other EA. For me the signals (Condition blocks) are working fine, the same way in both examples.

Yes, it is a simple question, I receive this question again and again, but the answer is not so simple. Check this post: post/7901

Then, try "Indicator appear". It generally works for this situation, but not always, it depends on the indicator and how it works.

It's confusing, I know. I also have troubles to decide what it should be, plus or minus. Try with minus on the left size, or if it's on the right side - plus.

At least this was my idea. This is like a snapshot of the project, but it also works as a project.

ok. managed to get what i wanted doing this
https://fxdreema.com/shared/zd6iwLeOb

Sorry...found it now.... Thank you..!

It works properly now 🙂 thank you

Not easily. The Comments that you can see now on the upper left corner of the chart is native from MQL4/MQL5. I will do something about this eventually, because people are asking questions like this from time to time, but now it's only the default Comment. Also, you can always create some Text objects here and there.

No, I didn't fixed the indicator, for me this is just another indicator from internet that fxDreema needs to work with. But sometimes fxDreema has bugs 🙂

Now I fixed the problem with that Symbol_ parameter, it appears where it should appear. But the other thing, the first problem I mentioned, I will leave it that way, because I want datatypes to be free. Well, some datatypes obviously does not fit. In this case "int" works.

Thank you.

Yes, this field is not only used to add a value, you can write whatever you want there and it will be put as it is in the final file. The content of this field is appended to the value of the operand, you can see how it works if you look at the code of that block.

__MetaTrader makes the EA to run and to do it's jobs, it's not self-executable. EAs are more like instructions that you add to MetaTrader. When you close MetaTrader, EAs also die with it.

That's why you can see advertisements of VPS servers here and there. VPS is normally used to host websites, for example this website is located on a VPS server, but some brokers offer VPS servers specialized for trading. Well, I never tried this, to be honest, so I don't know what is more special. I will suggest to ask somebody else about this :)[/quote:uw4oikcg]

Oww i see, ok thanks for the info

Thanks, these changes fixed it!