Rinse 'n Repeat

[Fibotrend]

Hi All,

I've noticed that after a correction the new trade in the direction of the trend opens with a gap.

Trade distance at 5pips/No offsetting - In the picture below you can see Trade5 opening at around 15 pips from the baseline at Trade4, the spread at that point was around 3 pips. I've seen this happening a few times and I was wondering if anyone has experienced the same. If not, I'd better change Criminal for my demo account.

Cheers

[SteveHopwood]

Most likely is that RnR suspended trading during a period when the spread was too wide to allow it.

[Fibotrend]

Most likely is that RnR suspended trading during a period when the spread was too wide to allow it.

That's what I thought so I switched off AvSpreadinput. However the gap is still happening and it does only when the baseline has to cross an open trade. Actually I've just noticed that it's doing the same thing again on the way up after T5.

I'll keep an eye on it this week and if I'm the only one experiencing this gap I'd better change Criminal

[SteveHopwood]

I am in for a tedious hour or so.

Westco28 has done a brilliant piece of bloop-spotting. Thanks Michael.

Line 2696:
ForceCloseTickets[cas] = ClosureTickets[cc];

should be
ForceCloseTickets[cas] = ClosureTicketsBuySide[cc];

Line 2811:
ForceCloseTickets[cas] = ClosureTickets[cc];

should be:
ForceCloseTickets[cas] = ClosureTicketsSellSide[cc];

These bloops affect RnR, HGBnG, GW and my three shells + retro-fitting mql file.

I have updated the version in post 1 but have not changed the version number.

I shall repeat this process in the relevant threads and give you guys the line numbers should you wish to make your own updates.

[Gertje]

I am in for a tedious hour or so.

Westco28 has done a brilliant piece of bloop-spotting. Thanks Michael.

Line 2696:
ForceCloseTickets[cas] = ClosureTickets[cc];

should be
ForceCloseTickets[cas] = ClosureTicketsBuySide[cc];

Line 2811:
ForceCloseTickets[cas] = ClosureTickets[cc];

should be:
ForceCloseTickets[cas] = ClosureTicketsSellSide[cc];

These bloops affect RnR, HGBnG, GW and my three shells + retro-fitting mql file.

I have updated the version in post 1 but have not changed the version number.

I shall repeat this process in the relevant threads and give you guys the line numbers should you wish to make your own updates.

Boy, am I lucky I only use these 3 EA's at the moment...
At least I'm in time to change these before the markets open!

[pipseee]

Boy, am I lucky I only use these 3 EA's at the moment...
At least I'm in time to change these before the markets open!

u dudes better B carefull with ur headBangin , u might still need it

just kiddin

[SteveHopwood]

It is Sunday night here in the UK, just over 90 minutes since the markets reopened after the weekend. I have seen 13 of my GJ trades close, at a net profit of 17 pips.

One pair of closures was a simple sell offset.

The second was a group of 11 buy trades closed by the single-sided complex offset, that did for a huge loser at the top of the pile. We already know that the double-sided complex code is working properly, so it looks as though the latest stuff is correct as well.

Thanks to all of you who helped with this. Bruster broke the back of it but the bloops you guys spotted have helped the development process enormously. Left entirely to me and my scatterbrained inability to think logically much beyond A + B = C, the development would have taken weeks, not days. You dun good, guys.

[dydynamic]

LET THE RUMBLE BEGIN

[pipseee]

LET THE RUMBLE BEGIN

u on live acct. atm :

[SteveHopwood]

u on live acct. atm :

Sorry, but I have to step in here. This is an environment for intelligent adults. It is an English speaking forum. Please refrain from using what I understand to be described as, "Text speak".

We require legible sentences using actual words, beginning with an uppercase letter and finishing with a full stop or question mark.

Stop 'contributing' if you are unable to write legible English.