Roonius,
Thanks for your weighting into the debate.
Firstly, apologies if you feel that my intent was to highjack the threat. This start of the conversation with Josh / NT support staff was a simple request for a status update on if this limitation was planning to be fixed in the next release. I was (as were others) less than impressed with the unhelpful responses we were seeing. Unfortunately, it would appear we have uncovered some bad culture in NT. I hope that it will be addressed in the near future.
Secondly, thank you for your suggestion on the best practice for the work around on the limitation for coding break-outs. Hopefully, now we have this tread back on track. Unfortunately, I’m not sure I understand your solution. It could well be better and more elegant than the one I suggest below.
My solution was to use onbarupdate() to check the current price, if it was close (e.g. 10 pips if trading forex) to the high-side breakout, then switch on a enterlongstop(). One could then use a int value to continue to track which order is switched on - .e.g. 0 = no order switched on, 1 = long switched on, 2 = short switched on. If price moves away from this towards the low side break out – then switch could be set to 2. I would then leave the relevant value switched on if the current price was within a specific distance from the break out price.
Please let me say, I have not coded this solution was yet. Once I have done so, I would be happy to share the code excepts when they are in place. Though, I have backed off coding this solution give we don’t know if next week a solution good be in place in NT7.
I have moved of working on a triple MA cross with ADX filters, mostly based on R C Allen’s initial work - http://www.streetauthority.com/terms/multiplemovingaverages.asp
Kind regards,
Dan
Comment