Topics created by ezzakt

Hi,

late reply from me - issue is solved.
Used a global Variable in your loop blocks to set the name.

But good to know I was not too blind to find it 🙂

Andy

Right, forgot to change to object description 😳

thanks 😉

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?

This indicator has 4 buffers, but they can't be detected for some reason... I have to check that later. But anyway, you can manually fill the data for 4 buffers - click on "new..." and write whatever you want to the input fields.
http://prntscr.com/25u3k0

At least this one seems to work for me: http://fxdreema.com/shared/2FeRN6Cod

In demo:

2013.10.30 13:56:03 '1218115382': remainder of order #75764982 was opened : #75764983 buy 0.50 EURJPY at 135.187 sl: 134.187 tp: 136.187 2013.10.30 13:56:03 '1218115382': order #75764982 buy 0.50 EURJPY at 135.187 sl: 134.187 tp: 136.187 closed at price 135.159 2013.10.30 13:56:03 '1218115382': request in process 2013.10.30 13:56:03 '1218115382': request was accepted by server 2013.10.30 13:56:03 '1218115382': close order #75764982 buy 0.50 EURJPY at 135.187 sl: 134.187 tp: 136.187 at price 0.000 2013.10.30 13:56:03 '1218115382': order was opened : #75764982 buy 1.00 EURJPY at 135.187 sl: 134.187 tp: 136.187 2013.10.30 13:56:03 '1218115382': request in process 2013.10.30 13:56:03 '1218115382': request was accepted by server 2013.10.30 13:56:03 '1218115382': order buy market 1.00 EURJPY sl: 134.187 tp: 136.187 2013.10.30 13:56:01 Expert MT4 EURJPY,H1: loaded successfully

In backtest:

2013.10.30 13:57:42 2013.09.11 00:00 MT4 EURJPY,M1: close #1 buy 0.50 EURJPY at 133.178 sl: 132.178 tp: 134.178 at price 133.158 2013.10.30 13:57:42 2013.09.11 00:00 MT4 EURJPY,M1: open #1 buy 1.00 EURJPY at 133.178 sl: 132.178 tp: 134.178 ok

And I always end up with 0.5 lots 🙂

In case of Buy trade, SL is initially below OP and cannot be placed above it, but if there is a big enough profit SL can be placed above OP, because SL depends on the current market price, OP does not matter.

When we have just placed Buy trade with SL of 100 pips, we know that SL level is 100 pips below it's OP, which is the current market price as well. And even when the price goes above/below a little bit, we still think that SL is 100 pips, because we accept that it SL is calculated as the difference between OP and SL level.

But what if we are in profit with 100 pips and we put SL 10 pips below? Then, how big is our SL if we measure it in pips? Can we now tell that SL is the difference between OP and SL level?

So, now I realize that this option (% of SL) is not very correct, because it is fine only when SL is below OP. Well, if we say that SL (in pips) is the difference between the last market price when we opened/modified our trade and SL level, then everything will be a little bit better. And in MQL4 we know Open Price of any trade, but unfortunately we don't know the last Modify Price, there is no such attribute in MQL4...

Then I decided that I can save that attribute in memory, but everything will be gone when the EA is turned off by accident, and the strategy will be bronek. So I decided that I can also backup that data in external file, but actually almost the same problem goes here - if you modify a trade manually or with another EA that does not operate with this external file, there will be wrong data again.

On another EA I can see its calculating SL and TP sizes wrong now. Ohoh 😐

see screenshot

Just as a comparison, if thats not printing, I dont know it ^^

......
symbol.png

that sound promising 🙂

Not really aware but the information you posted should be enough to get it done.

Thanks as always, cheers

In any case it's better if the indicator gives proper signals to it's buffers, but objects can be used too.

ok, well that will work but it gets really complicated when doing this...depending on if you export tick data with or without weekends...and so on

So would appreciate a block that checks on "current day"
That would be great

Cheers

The normal way is to use buffers of course, not the objects. There is a block with name like "Levels tester..." that can show visually how any buffer behave.

ok I will try this and post the results here

Hi there,

sorry for the late reply.
I did test the strategy you created and thats exactly what I meant. So the function works as expected.

And yes you are right, that strategy is not final 😉
Found some good settings while optimizing in backtester, but the strategy needs some more logic to get better...have to think about that

Thanks again for your help, cheers

Andy