I don't trade options but writing a separate (must be separate or in
another thread because of blocking) program to send keystrokes
(enter) or mouseclicks to a window at a predefined spot isn't that
complex. I don't know what the options window looks like (I don't
trade options) or if the "no" button defaults (rendering a simple
enter keystroke unusable).
The basic concept is to figure out the unique qualities of the popup
window you are searching for (if any) by using a program like
Microsoft's SPY++. Then when the window you are looking for appears
you either send a set of keystrokes to the window or a mouse click to
the correct spot to kill the window. The program that does this
should probably only have one function - to kill the dialog, and
should just sit there looping, waiting for that dialog to pop up and
then it zaps it. I do this for the ActiveX "Accept Incoming
Connections" dialog so that my program can log into TWS without any
intervention on my part.
--- In twsapi@y..., "qnolte" <q1@n...> wrote:
The option confirmation requirement is a real problem for me also.
I
didn't realize that the real problem is the option exchanges
rules.
Can anyone come up with a screen scrapper that could see the popup
confirmations and automatically response to them?
--- In twsapi@y..., "dtkamp" <dkamp@e...> wrote:
"i hear options trigger TWS pop-ups so i can't have a
true program trading platform in place :("
Hi Jason. You may know this, but for others reading the above,
it's
the option exchanges that don't allow automated option trading -
IB
is just following their rules.
With respect to Java, I bet you actually get a lot of us avoiding
it
just because of the limitations we see in the Java-based TWS. In
other words, you can get an immediate edge over TWS just by not
using
Java (at the cost of cross-platform potential).
