btw,
Have you been able to call connect, and then call
disconnect and then call connect again? The second
call to connect always seems to cause an exception
inside the API, for me anyway.
--- Todd Turner <todd_a_turner@...> wrote:
I believe that the callbacks only occur during a
call
to requestData().
In my initial testing I used Sleep with no problem.
I
now have Windows sending a WM_TIMER message to my
apps
message queue every 250 msecs now.
--- usernew <no_reply@...> wrote:
Yeah, I tried that and got exceptions. The problem
might be that when
you sleep the whole thread is put to sleep, so the
event tickprice
etc. callbacks can't happen. So, a regular sleep
might not work well
in this case.
--- In twsapi@y..., Todd Turner
<todd_a_turner@y...>
wrote:
I am not familiar with Java, but you need some
sort of
system call Sleep(int timeout_msecs), so that
the
process blocks until the timeout occurs. This
functionality is provided by the OS.
--- usernew <no_reply@y...> wrote:
My program currently is structured as follows:
class TWS implements EWrapper {
public void requestdata(...)
public void tickPrice(...)
public void tickSize(...)
...
public void wait_trans() {
for(i=0; i < xxxxx; i++);
}
}
public class Main {
tws.connect();
for(i=0; i<n; i++)
tws.requestdata(...)
tws.wait_trans();
tws.disconnect();
}
Is there a better way to structure this
program
?
My concern is wait_trans(). It is continuously
eating up cycles. My
program does not need to do anything while it
is
waiting for the
arrays to be populated, but I would still like
to
wait without
consuming cycles.
Thanks in advance
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
