@Yusi
Was going through your helpful posts now. As I have mentioned elsewhere in TJ, the problems/questions/facts that face a wannabe auto trader using AMI-Nest combination are:
a) repainting of signals (as you mentioned) is problematic for people using gfdl based plugins using Immediate option because the order has been placed at first appearance and if the trend now reverses the signal won't be repeated, leaving an orphan trade.
b)painting of "rogue" signals, such as a buy after a buy, instead of a sell. I can hazard a guess that this is manageable by the afl code but have so far not received any concrete suggestion for a remedy.
c) plug ins/APIs/Bridges to make the OMS and the afl talk to each other in passing variables and parameters back and forth will greatly contain the damages a) and b), but they are not found, at least not easily. There are claims that are not borne out by a demo.
d) is the Nest + (trading plugin) a virtue or a vice? Two developers demonstrated remotely that by NOT using N+ and using a different system I could trade auto even in MCX. It beats me why brokers are stuck (may be they are helpless), and would like to get some illumination on this point.
e) issues that Nest Plus/GDFL has with Windows 8. The afl works fine but not the auto part, giving a COM error (which you mentioned).
Interestingly, one very reputed platform provider agreed that it was a risk that an afl produced an orphan trade due to a missed trade by sudden price movement but they demanded money to add this security protection, calling it a non-essential feature.
Was going through your helpful posts now. As I have mentioned elsewhere in TJ, the problems/questions/facts that face a wannabe auto trader using AMI-Nest combination are:
a) repainting of signals (as you mentioned) is problematic for people using gfdl based plugins using Immediate option because the order has been placed at first appearance and if the trend now reverses the signal won't be repeated, leaving an orphan trade.
b)painting of "rogue" signals, such as a buy after a buy, instead of a sell. I can hazard a guess that this is manageable by the afl code but have so far not received any concrete suggestion for a remedy.
c) plug ins/APIs/Bridges to make the OMS and the afl talk to each other in passing variables and parameters back and forth will greatly contain the damages a) and b), but they are not found, at least not easily. There are claims that are not borne out by a demo.
d) is the Nest + (trading plugin) a virtue or a vice? Two developers demonstrated remotely that by NOT using N+ and using a different system I could trade auto even in MCX. It beats me why brokers are stuck (may be they are helpless), and would like to get some illumination on this point.
e) issues that Nest Plus/GDFL has with Windows 8. The afl works fine but not the auto part, giving a COM error (which you mentioned).
Interestingly, one very reputed platform provider agreed that it was a risk that an afl produced an orphan trade due to a missed trade by sudden price movement but they demanded money to add this security protection, calling it a non-essential feature.