comparing order objects

[junkone]

which is better?
comparing the order names or the order objects?

• execution.Order.Name==entryOrderLong.Name
• execution.Order==entryOrderLong

[NinjaTrader_CodyB]

Hello,
One of these would not be better than the other unless you are specifically needing the name or the order object for some circumstance.

[junkone]

I am reading the comments in your documentation.
Are you suggesting that if I assign the orderobject when I submit the order, it will not have a reliable data on it? should I reassign it again in orderupdate?

entryOrderLong=SubmitOrderUnmanaged(0, OrderAction.Buy, OrderType.Market, DefaultQuantity, 0, 0, "", "bounceStates.watch4longbounce");

QUOTE]

protected override void OnExecutionUpdate(Execution execution, string executionId, double price, int quantity, MarketPosition marketPosition, string orderId, DateTime time)
{
// Assign entryOrder in OnOrderUpdate() to ensure the assignment occurs when expected.
// This is more reliable than assigning Order objects in OnBarUpdate, as the assignment is not gauranteed to be complete if it is referenced immediately after submitting
if (order.Name == "Enter Long" && orderState == OrderState.Filled)
entryOrder = order;
}

[/QUOTE]

[junkone]

appreciate an update!!

[NinjaTrader_CodyB]

Hello,
Can you clarify what you are meaning by reliable data?
If you are checking on a fill in OnExecution() or the status of an order in OnOrderUpdate() you will need to have the order assigned in OnExecution() or OnOrderUpdate to ensure that it is when the order or fill is actually active.

[junkone]

my concern about reliability is due to your coments in the documentation..., I assign the Order objects in my onBarupdate when I submit the order. I am assuming that the Order object is maintained reliably. Please clarify..,

protected override void OnExecutionUpdate(Execution execution, string executionId, double price, int quantity, MarketPosition marketPosition, string orderId, DateTime time)
{
// Assign entryOrder in OnOrderUpdate() to ensure the assignment occurs when expected.
// This is more reliable than assigning Order objects in OnBarUpdate, as the assignment is not gauranteed to be complete if it is referenced immediately after submitting
if (order.Name == "Enter Long" && orderState == OrderState.Filled)
entryOrder = order;
}

[NinjaTrader_CodyB]

Hello,
If you assign an IOrder to a variable in OnBarUpdate(), you cant directly access it from OnBarUpdate() right after you assign it because it may or may not be null at that time:

IOrder myOrder; 

protected override void OnBarUpdate()
{
  myOrder = EnterLong();
  Print(myOrder.AvgFillPrice);
}

This is not assigned yet.

Instead, using OnOrderUpdate() you are guaranteed it will be not null or at least be more updated than the prior example.