开云体育

Just guessing here, Edward, but this is probably related to the new field and feels like a regulatory thing for brokers and advisors. So I guess unless you are a broker or advisor, pass the empty string.

闯ü谤驳别苍

From:

Limit Order With Manual Order Time

The Limit Order With Manual Order Time is a with ManualOrderTime property.

Order order = OrderSamples.LimitOrder(action, quantity, limitPrice);

Placing a Limit Order With Manual Order Time
The Manual Order Time field is required for, and becomes editable for, "manual" orders, which are orders that originate from a client (whether by phone, email, chat, verbally from the floor, from another desk, etc.) and are then entered into the system. The Manual Order Time field is not used for client orders received electronically, nor for orders that originate from the account manager (with discretion) in the client's accounts, or when an order is allocated to ALL accounts or among multiple accounts using an account group or model portfolio.

client.placeOrder(nextOrderId++, ContractSamples.USStockAtSmart(), OrderSamples.LimitOrderWithManualOrderTime("BUY", Util.StringToDecimal("100"), 111.11, "20220314 13:00:00"));

Canceling a Limit Order With Manual Order Time
The Manual Order Cancel Time field is required for, and becomes editable for, "manual" order cancelations, which are order cancelations that originate from a client (whether by phone, email, chat, verbally from the floor, from another desk, etc.) and are then entered into the system. The Manual Order Cancel Time field is not used for client orders cancelations received electronically, nor for orders that originate from the account manager (with discretion) in the client's accounts, or when an order is allocated to ALL accounts or among multiple accounts using an account group or model portfolio.

client.cancelOrder(nextOrderId - 1, "20220314 19:00:00");

No problem, Ed.

If you follow the call path in the Java API source code you will find that either option (null or "") is fine and yields the same result. The Order class uses Order.EMPTY_STR to initialize manualOrderTime and you could use that, since it is a public constant. It happens to be defined as "".

闯ü谤驳别苍

? ? def cancelOrder(self, orderId:OrderId, manualCancelOrderTime:str):

Scott did not tell us, which TWS API version caused the issue. But I suspect it is 10.30 or higher.

• from cancelOrder(self, orderId: OrderId, manualCancelOrderTime: str)
• to cancelOrder(self, orderId: OrderId, orderCancel: OrderCancel)

That is true for all languages, not just Python. The new class OrderCancel has several fields, among them a string field called manualOrderCancelTime.

Programing languages other than Python should give you compilation errors since the second argument changed from type String to type OrderCancel.?Also, cancelOrder requests will likely fail unless and instance of OrderCancel is passed. An object with default fields might work, but I have not checked that.

If in doubt, the source code is still the best documentation, Scott.

I am not a Python practitioner, but I assume the OrderCancel class has a no-argument constructor that initializes the four fields with meaningful "empty" values. At least the Java implementation has one. Assuming you cancel orders infrequently, I'd replace the empty string "" parameter with something like new OrderCancel()?or the equivalent in Python.

My framework already has a convenience method void cancelOrder( int orderId ) that hides the extra parameters from the business logic (since I don't need the manualCancelTime or OrderCancel logic). In that case, a single shared and constant OrderCancel object will work, too.

闯ü谤驳别苍

?

?