Multi 10:4 Trader EA

[Jonathan2FI]

Dash Question ref. V2,

Simplex, Andy,
Dashboard works perfectly on the big screen with brokers Alpari and Axi - all in view even the totals and delete all.... buttons at the bottom ..
On the laptop with GKFX different story ...can't see the bottom (understand scrolling a chart does not work and scale does bugger all or?) so I tried adding ignore pairs to see if I could get to the bottom - failed just a big black gap minus 12 pairs.

Wanted to share a work around that may or may not appeal - since this EA needs to run all the time you need a decend on all the time desktop (plus power protection) and or a VPS. I have had probs in the past with duplicate access and trades occuring when I log on to VPS from 2 different computers so now everying goes through the trading desktop including logon to VPS. When I access the desktop remotely from my laptop using logmein (free service) I can scroll up and down and see full dashboard and control all buttons etc. voila

Its a real pleasure to use the EA and Dash - it gives more opportunity to think rather than develop navigatation skills across 20+ charts. Best I have seen.
Jonathan

[simplex]

Dash Question ref. V2,

Simplex, Andy,
Dashboard works perfectly on the big screen with brokers Alpari and Axi - all in view even the totals and delete all.... buttons at the bottom ..
On the laptop with GKFX different story ...can't see the bottom (understand scrolling a chart does not work and scale does bugger all or?) so I tried adding ignore pairs to see if I could get to the bottom - failed just a big black gap minus 12 pairs.

Jonathan

Jonathan,

Yes, I faced the same when moving from full HD development to smaller test machine. Andy hardcoded the button coordinates. In my 1.08 modification I did it the following way:

Code: Select all

		CloseAllButtonY = footCellTop + 60;

Thus the buttons are placed 60 pixels below coordinate footCellTop.

@Andy: could you consider using such relative coordinates? IMO would make code maintenance easier.

@Jonathan: to provide a quick hack for your issue, try the following:

Code: Select all

int init() {
 hwnd=WindowHandle(Symbol(),Period());
   
   tbRemoveAll(hwnd);   
   btnRefresh = tbPutObject(hwnd, "button", 715 , 650, 155, 20, "Delete Pending");
   btnCloseAll = tbPutObject(hwnd, "button", 890 , 650, 155, 20, "Close All Open Trades"); // hwnd,type,x,y,w,h,label
   btnDeletePending = tbPutObject(hwnd, "button", 1065 , 650, 155, 20, "Delete Pending");
   /*   ORIGINAL SETTINGS FOLLOWING ...
   btnRefresh = tbPutObject(hwnd, "button", 715 , 730, 155, 20, "Delete Pending");
   btnCloseAll = tbPutObject(hwnd, "button", 890 , 730, 155, 20, "Close All Open Trades"); // hwnd,type,x,y,w,h,label
   btnDeletePending = tbPutObject(hwnd, "button", 1065 , 730, 155, 20, "Delete Pending");
   /*

Then recompile. This worked for me. If not, play around with the 650 parameters for all 3 buttons. This is the vertical position of the buttons, counted in pixels from top of chart window.

Good luck,

simplex

[Jonathan2FI]

Hey Guys,
I'm so happy to see you all pointing out so many bugs. I'll pitch in some myself.

Regarding the different trades on different brokers, I suggest we benchmark one broker for comparing results. Same stuff is happening all over at the DBM thread. So nothing new here, it's broker feed IMO and I suggested the same thing to Bunks too.

DeletePendIfMACross: The pendings are auto delete if MA cross is set to true. The pends will re-populate in next h4 bar if no MA cross and conditions are met.

Andy confirmed to this. "Yes if we change sides the ea will start to build if the conditions are correct."
I suggest a change here. If the PA crosses to the other side, then either
1. No more trades for that day
or
2. No more trades in that H4 candle hour.
What I see contrary to this is that as soon as the PA crosses back into original territory, it starts taking orders even though the current bar has peeked to the other side of the MA and retraced. Thus better would be to not take any more checks or orders if the current H4 has peeked across or current D1 has peeked across. Something on these line TIB suggests too.

Sell : Say at any point if the conditions are true, next SR is MR1, TP is MSR2. How many pends will be set, 4? MR1, P, MS1, S1. TP for all this will be MS2?

Please confirm this, someone. I'm getting couple trades that I think are wrong if above stated is true.

great work, I like the new buttons, ...

Sure U do, so do we. Thanks, you're a Champ !

Ok I'm jealous now ...

Don't have to be, just go live and the feeling will reciprocate. Thanks for the signature.

@ Andy : AO, Oh ho, here we go, ... again. Cheers !

Regards to All, Max.

I see your point ref. AUDJPY today evidence of multiple closes of pending buystops attached where new pendings were placed after 240 breached and PA remained on the invalid side ....since 1/4/2013.
I agree remove these filter with no more trades today on pair if price x 240 (high or low not close).
- must keep out of wipsaw trades around 240 where we place our stops.
See Screen shot
Jonathan

[MrLong]

Dash Question ref. V2,

Simplex, Andy,
Dashboard works perfectly on the big screen with brokers Alpari and Axi - all in view even the totals and delete all.... buttons at the bottom ..
On the laptop with GKFX different story ...can't see the bottom (understand scrolling a chart does not work and scale does bugger all or?) so I tried adding ignore pairs to see if I could get to the bottom - failed just a big black gap minus 12 pairs.

Wanted to share a work around that may or may not appeal - since this EA needs to run all the time you need a decend on all the time desktop (plus power protection) and or a VPS. I have had probs in the past with duplicate access and trades occuring when I log on to VPS from 2 different computers so now everying goes through the trading desktop including logon to VPS. When I access the desktop remotely from my laptop using logmein (free service) I can scroll up and down and see full dashboard and control all buttons etc. voila

Its a real pleasure to use the EA and Dash - it gives more opportunity to think rather than develop navigatation skills across 20+ charts. Best I have seen.
Jonathan

Hi Jonathan,

Thanks for your feedback.

I've worked out how I'll sort the button and cell height,
we already have the variables within the EA for screen width and height, so
should be straight forward, it all works perfect on my screen, but we had
so wait for feedback from you guys.

Thanks
Andy

[MrLong]

Dash Question ref. V2,

Simplex, Andy,
Dashboard works perfectly on the big screen with brokers Alpari and Axi - all in view even the totals and delete all.... buttons at the bottom ..
On the laptop with GKFX different story ...can't see the bottom (understand scrolling a chart does not work and scale does bugger all or?) so I tried adding ignore pairs to see if I could get to the bottom - failed just a big black gap minus 12 pairs.

Jonathan

Jonathan,

Yes, I faced the same when moving from full HD development to smaller test machine. Andy hardcoded the button coordinates. In my 1.08 modification I did it the following way:

Code: Select all

		CloseAllButtonY = footCellTop + 60;

Thus the buttons are placed 60 pixels below coordinate footCellTop.

@Andy: could you consider using such relative coordinates? IMO would make code maintenance easier.

@Jonathan: to provide a quick hack for your issue, try the following:

Code: Select all

int init() {
 hwnd=WindowHandle(Symbol(),Period());
   
   tbRemoveAll(hwnd);   
   btnRefresh = tbPutObject(hwnd, "button", 715 , 650, 155, 20, "Delete Pending");
   btnCloseAll = tbPutObject(hwnd, "button", 890 , 650, 155, 20, "Close All Open Trades"); // hwnd,type,x,y,w,h,label
   btnDeletePending = tbPutObject(hwnd, "button", 1065 , 650, 155, 20, "Delete Pending");
   /*   ORIGINAL SETTINGS FOLLOWING ...
   btnRefresh = tbPutObject(hwnd, "button", 715 , 730, 155, 20, "Delete Pending");
   btnCloseAll = tbPutObject(hwnd, "button", 890 , 730, 155, 20, "Close All Open Trades"); // hwnd,type,x,y,w,h,label
   btnDeletePending = tbPutObject(hwnd, "button", 1065 , 730, 155, 20, "Delete Pending");
   /*

Then recompile. This worked for me. If not, play around with the 650 parameters for all 3 buttons. This is the vertical position of the buttons, counted in pixels from top of chart window.

Good luck,

simplex

Hi Jurgen,

Yes sounds good.

Andy

[slipshod]

A last question for today (really must sleep) ... would it be possible to add buttons beside each pair that show Yes or No for whether Longs and Shorts are allowed. They'd act as toggles - user clicks on one and it changes to the opposite value. Then if obviously one is set to No, the EA deletes pending trades in that direction and won't enter any new ones, but will consider trades in the direction that has a Yes beside it.

I'm thinking of situations where, for reasons external to 10.4, the trader might be reticent to trade in a certain direction, but doesn't want to add the pair to the exclude list in case the EA identifies a trade in the direction they think it might go. Just such an example happened today on GBPCHF - I could see a strong reversal pattern leading me to believe it'd drop (which it has) but a pullback's hooked the EA into a long that's rapidly running for its stoploss.

[theforexedge]

A last question for today (really must sleep) ... would it be possible to add buttons beside each pair that show Yes or No for whether Longs and Shorts are allowed. They'd act as toggles - user clicks on one and it changes to the opposite value. Then if obviously one is set to No, the EA deletes pending trades in that direction and won't enter any new ones, but will consider trades in the direction that has a Yes beside it.

I'm thinking of situations where, for reasons external to 10.4, the trader might be reticent to trade in a certain direction, but doesn't want to add the pair to the exclude list in case the EA identifies a trade in the direction they think it might go. Just such an example happened today on GBPCHF - I could see a strong reversal pattern leading me to believe it'd drop (which it has) but a pullback's hooked the EA into a long that's rapidly running for its stoploss.

Slipshod / Andy

Maybe also a pip buffer above / below the Pivot Lines, as that's usually where the brokers do their stop hunting before taking the market up/down.

when I'm trading 10.4 manual I never place my Pending's on the Pivots - usually +5/10 pips, also never on round numbers..

JP

[mobthehop]

slipshot,
thanks for all your bug hunting and corrections....
If you do not mind me saying,

Its not a choice whether to use Stoch or RSI. You can use both or either.

does not comply with the 10.4 either, it should be either/or and SH expressed his preference for RSI....

As Stoch and RSI are defined as variables, would it not make more sense to set only one of them as external boolean and when set to false, the other is considered true (eg external bool RSI = true, if set to false, Stoch will be applied without being an external)

Just a thought, not a criticism...

Mop

PS: Thank you very much for your pending order script - use it all day long....

[MrLong]

A last question for today (really must sleep) ... would it be possible to add buttons beside each pair that show Yes or No for whether Longs and Shorts are allowed. They'd act as toggles - user clicks on one and it changes to the opposite value. Then if obviously one is set to No, the EA deletes pending trades in that direction and won't enter any new ones, but will consider trades in the direction that has a Yes beside it.

I'm thinking of situations where, for reasons external to 10.4, the trader might be reticent to trade in a certain direction, but doesn't want to add the pair to the exclude list in case the EA identifies a trade in the direction they think it might go. Just such an example happened today on GBPCHF - I could see a strong reversal pattern leading me to believe it'd drop (which it has) but a pullback's hooked the EA into a long that's rapidly running for its stoploss.

Slipshod / Andy

Maybe also a pip buffer above / below the Pivot Lines, as that's usually where the brokers do their stop hunting before taking the market up/down.

when I'm trading 10.4 manual I never place my Pending's on the Pivots - usually +5/10 pips, also never on round numbers..

JP

Hi,

We already have that one in place calculated by the ADR. I have a switch somewhere at the top of the code if switched to true and recompiled will give an alert with each pairs settings, when you have the settings, switch the switch back to false and recompile.

Andy

[MrLong]

A last question for today (really must sleep) ... would it be possible to add buttons beside each pair that show Yes or No for whether Longs and Shorts are allowed. They'd act as toggles - user clicks on one and it changes to the opposite value. Then if obviously one is set to No, the EA deletes pending trades in that direction and won't enter any new ones, but will consider trades in the direction that has a Yes beside it.

I'm thinking of situations where, for reasons external to 10.4, the trader might be reticent to trade in a certain direction, but doesn't want to add the pair to the exclude list in case the EA identifies a trade in the direction they think it might go. Just such an example happened today on GBPCHF - I could see a strong reversal pattern leading me to believe it'd drop (which it has) but a pullback's hooked the EA into a long that's rapidly running for its stoploss.

We could do that with check boxes, but we need to find the room, we can select all the settings with
Radio buttons and checkboxes.