Announcement

Collapse
No announcement yet.

Partner 728x90

Collapse

too many OnOrderUpdate events

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    too many OnOrderUpdate events


    I'm setting a stop loss thats triggering OnOrderUpdate 3 times.

    Code:
    if (order.Name == stopLossName)
    dbMsg("set stop loss to " + Math.Round(stopPrice, 2).ToString());
    should I filter out the unwanted ones? if so what's the best way?

    #2
    Why don't you print the OrderState as well?

    I bet you each call to OnOrderUpdate will have a different state.

    Comment


      #3
      Hello fingers,

      OnOrderUpdate is called each time an order managed by a strategy changes state.

      The Help Guide page below lists all the states an order can have:


      I agree with bltdavid's suggestion of "filtering the unwanted ones" by using a check for OrderState. It's up to you which order state you want the information from.

      If you have any further questions, please let us know.
      Gaby V.NinjaTrader Customer Service

      Comment

      Latest Posts

      Collapse

      Topics Statistics Last Post
      Started by laketrader, 03-10-2025, 07:20 AM
      7 responses
      66 views
      0 likes
      Last Post laketrader  
      Started by juletjak, Today, 07:37 PM
      0 responses
      2 views
      0 likes
      Last Post juletjak  
      Started by stafe, 03-10-2025, 04:46 PM
      5 responses
      59 views
      0 likes
      Last Post MiCe1999  
      Started by VFI26, 03-21-2025, 11:21 AM
      2 responses
      28 views
      0 likes
      Last Post MiCe1999  
      Started by algospoke, 03-12-2025, 07:41 PM
      2 responses
      34 views
      0 likes
      Last Post algospoke  
      Working...
      X