Posts made by fxDreema

Maybe this option is not very good, or the way the block reacts to it. These blocks are pretty old now, I have idea to get rid of them and move their functionality into "Buy now" and "Sell now" blocks as MM options... but when, if, how... I don't know

This option "Maximum volume size" often makes me wonder what is going on as well

http://www.alpari.com/research-tools/ea-builder
http://www.ironfx.com/en/ea-builder

After the backtest everything you see is from the last moment of the candle. And when you values to detect signals from the current candle, they are temporary, especially in the beginning of the candle (when Once per bar is on the top). When Once per bar is below the conditions, then you work with the middle of the current candle. To work with finished candles, set Candle ID to 1 everywhere. In this situation I got this: http://prntscr.com/2loqu5

When "Once per bar" is on the top, then what is below works at the first tick on every new bar. At this moment the candle is still new and it looks like nothing, or at least does not look the way you see it after the backtest ends. So, when indicators are used for the current candle (when Candle ID = 0), then where "Once per bar" is placed matters, it's different if it is below or above conditions. If Candle ID is something bigger than 0, then no problem, it will be the same, because operands in the condition will not change until the end of the candle.

If you really want to use the current candle, then I can suggest to put "Once per bar" blocks below conditions. This is what I got with setup like this: http://prntscr.com/2lo8q3

I think I have to remove one rule in "Once per minutes". Now this block can be active for 1 minute every X minutes. If it is set up for 5 minutes, then it can be active in minutes between 5-6, 10-11 and so on... Now that I think about it, this maybe only causes problems and it's not useful.

But what about "Once per bar", isn't it working with it? Because this is as it sounds - it can pass once per bar, no matter where are you inside the bar - in the beginning, in the end. And for things like indicators that have the bar in their nature I think this is the block to be used.

From a long time ago I wonder what name to give to these blocks that starts with "Once..." if I just add some simple option to make them able to work not only once, but more than once. But "Once per bar", "Once a day" and others sounds so clear now, how to ruin those names.

From your opinion, will it be better if I add option inside and rename them to something else that is not "Once"? And what word to use instead "Once"?

Otherwise if you connect second "Once" block to the yellow output of the first one, it will work for this idea.

So it is martingale, as I suspected. This block checks the last trade, and because partial close produce brand new trade, it just reads it's lot size. And it's not that it can't use the initial lot size (if I change something in the code), but what if someone wants to use it as it is now. Or I should add one more parameter for this block

How do you calculate next trade's lot? It obvously uses the last known lot size (0.01) instead of the initial one (0.1).

gReferansHigh_1 is some variable that is used from this EA to hold value. How this variable is used outside these conditions... I can't tell. But you can search for it in the code and you will see where it is defined (this will be like "double gReferansHigh_1...") and where it is used.

There are at least 2 ways.

• One way is under "on Tick" - something like: No trade is running -> Check last closed trade profit -> Delete pending orders
• The other way is under "on Trade": (on trade) Trade closed -> Condition (where you will check the profit, use (on trade) category) -> Delete pending orders

I think I prrefer the first way, because in MT4 for "on Trade" to work extra resource is needed, but only if you have some blocks there

The minimum lot size cannot be changed, this comes from the broker. Here is a small test that opens 0.2 lots and then closes 0.11 lots. At the end I have a single trade of 0.09 lots, which is interesting because otherwise I cannot open something smaller than 0.1 lots and I also cannot close lot size smaller than 0.1 lots.

Yesterday I found small problem with "close (partially)" block, but I think it was only for the web version. Can you try this example? At least for me it works, here is the result: http://prntscr.com/2lgasg

Yes, I should write guide for money managements, these things also confuses me

"% Equity" is something that I added in the beginning, but it turns out to be stupid and sometimes I think to remove it. If you have EURUSD where 1 lot is 100,000, and you have equity of 10,000 dollars, then 100% of equity (which is 10,000) will be transformed into lot size of 0.1. You know, 0.1 lot is 10k of money. If you have equity of 15k, then the lot size will be 0.15.
The problem with this method is that other markets have different lot size value or they use different currency. If you try this on Gold... I don't know what crazy lot size it will take.

"Freeze % of Equity" calculates lot size depending on the leverage, so it will freeze certain amount of money. See at the "Free margin" and "Margin". Here is before and after I use 10% of equity.
http://prntscr.com/2lat4o
http://prntscr.com/2lat9r
"Margin" becomes something like 10% of the equity that was before opening that trade.
This MM should work also with markets that has nothing to do with the deposit currency, but I think in this case any backtest will be wrong.

I don't know for emails for sure, because I never tested that for me seriously, but I know there are people using this.

In the email block very simple and native MQL4 function is used (SendMail()), so there is pretty much nothing there created by me. What this blocks do is to construct the message and use that function to send it.

If you think that signalling can be slow, which is not impossible, you can put Print message or Alert message before or after the email block... maybe after... so you will see when exactly things happen. Well, I'm not sure whether SendMail() if synchronous or not (whether it will wait for the function to finish before continue), but most of the things in MT4 are.

Pips away from stop-loos means that the current price should be above SL+Pips (for buys) or below SL-Pips (for sells). So, if you have for example buy with SL=300 pips, then "pips away from stop-loss" with setting at 100 pips will be true from the beginning, because initially the current price is 300 pips away from SL.

Close partially can close "wrong" lot sizes depending on what is the minimum lot size and lot step from the broker. Partial close actually closes the current and then opens new trade. For example I have minimum lot 0.1 lots, so I can't close 0.09 lots from 0.1 lots. If I try really I get this error "Invalid trade volume (131)", but in fxDreema it uses the minimum lot size that is possible, so instead of error message I have 0.1 lot closed.

I can suggest "once per trade/order" block if you have situation where the trade is partially closed few times in a row.

In MetaTrader go to Tools->Options->EMail tab

I tried it now, it is ok for me. Maybe it stopped downloading or something like this. And if you are with IE, I'm not sure it will actually re-download the file. So my suggestion is to try again or with another browser. Otherwise this is WinRar SFX archive and you can also open it with WinRar - there is "fxdreema.exe" and empty "Data" folder there.

Може да проверяваш които искаш точки поотделно. В Condition има Candle -> Candle Close (или който и да е параметър на свещта), и там можеш и да зададеш от коя валутна двойка да търси информация и от коя свещ, и от кой период. Но не виждам какво точно ще откриеш като сравниш две точки дето са примерно 1.3287 и 1.5736... някакви си две безлични стойности. Но може и аз да съм се объркал за това каква ти е идеята. Ако това ти трябва - там е. Само че не би работило на бектест, че МТ4 не може да бектества други двойки различни от настоящата

You tried that?

iCustom allows many input parameters without giving error message.
This gives this error:

iCustom(1,2,3,4);

This does not:

iCustom(1,2,3,4,5);
iCustom(1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17);

so if it have more than 4 parameters - everything is ok with this function, it does not actually read if something in the indicator is right or wrong.
http://docs.mql4.com/indicators/icustom
This function IndicatorMoreShift() should work without parameters. So from that screenshot for me everything looks fine, or at least I can't recreate this here.
Is it possible that another function is responsible for this error?