Author |
Topic: OECClient_OnCommandUpdated() modifies for execution (3 messages, Page 1 of 1) |
||||
---|---|---|---|---|---|
Moderators: VPfau | |||||
DBrubaker673 Posts: 55 Joined: Jul 18, 2007 |
When a Stop Market order is executed, you are throwing me anOECClient_OnCommandUpdated() event with CommandType.Modify (CommandStete.Executed) just before you throw the execution event (fill). So my software thinks I have modified an order, when in fact the only thing that has happened is that you have executed it.
Questions: 1. Can you stop throwing the Modify event in this case? or 2. Is there some other way my software can detect that this modify event is spurious. Note that there are no fills yet when this event is received. It seems to look just like a real (e.g price) mofification. Thank you, Dale |
||||
SergeK -Developer- Posts: 475 Joined: Jan 26, 2007 |
the event was raised due to order modified from STP to MKT. (or from STPLMT to LMT). We could not prevent this event from raising, but you can detect it either by comment "auto-updated" or just by knowing that you did not initiate this modification.
|
||||
ZHu34 Posts: 3 Joined: Oct 13, 2008 |
Moved
Edited by ZHu34 on Oct 13, 2008 at 03:31 PM |
||||