--- In twsapi@y..., "marinindextrader" <marinindextrader@y...> wrote:
But the questions remains...How do you flag an OCA group when
sending
to/through the TWS?
There is no param that defines the group. Only on the reqOpenOrder
is
their any refrence in my documentation as to OCA?
I would agree that it should be there and is of value. But where is
it defined on an upstream order send?
The oca group is one of the strings within the order
structure/object. I dont know about the ActiveX thing, but at the
lower level, within the order structures is a string for the oca
group name. Just fill it in before you place the order.
FWIW, i've given up completely on all the ib supplied code, and now
have my own stuff deal directly with the sockets. On the c++
wrappers they provided, the oca group is one of the CString objects
within the order itself, so I would expect it's a property of the
activeX version.
By re-writing everything, i've narrowed down the problems to one
single outstanding problem, for which there is no cure short of
fixing tradeworkstation. I'ts on the 'nextid' stuff.
Using the last one given to you from the nextid callback is NOT safe,
remember this, that same number has been given to ALL programs
talking to tws. The safe way, is to request a block, then wait, and
see that the next one it says, is that far beyond the block you
requested. Now you know, the block is yours, and wont be used
elsewhere. The problem is, if 2 clients request at the same time,
there's no way to tell, which client got which block, at least that's
how it'll work with way the original c++ wrappers were built, so i'm
assuming the logic inside the ActiveX is just as broken.
We've redone that logic as best we can, and it 'appears' to be safe
so far, but only time will tell.
