|
PureBytes Links
Trading Reference Links
|
I'd feel better if it was a little more of a team effort.
Jim Bronke
Phoenix, AZ
----- Original Message -----
From: "Craigbud" <craigbud@xxxxxxxxxxx>
To: "Jim Bronke" <jvbronke@xxxxxxxx>; <prosys@xxxxxxxxxxxxxxxx>; "Mark Baze"
<mark_baze@xxxxxxxxx>
Cc: "Omega-List" <omega-list@xxxxxxxxxx>
Sent: Wednesday, August 01, 2001 7:37 PM
Subject: Re: Addendum: "New Orders" dialog box problem
> Probably takes only one good 32 bit programmer who knows how to implement
> what Windows offers, and fix in a flash all the 2000i beta insults that
> hired-for-cheap programmers created --during a time when management fell
> out of love with analysis software, and salivated over what was going on
> with the broker business during the NASDAQ boom of 1998-2000.
>
>
> At 12:05 PM 8/1/2001, Jim Bronke wrote:
> >One little ol' programmer?
> >
> >Jim Bronke
> >Phoenix, AZ
> >
> >
> >
> >----- Original Message -----
> >From: "M. Simms" <prosys@xxxxxxxxxxxxxxxx>
> >To: "Mark Baze" <mark_baze@xxxxxxxxx>
> >Cc: "Omega-List" <omega-list@xxxxxxxxxx>
> >Sent: Wednesday, August 01, 2001 11:32 AM
> >Subject: RE: Addendum: "New Orders" dialog box problem
> >
> >
> > > Mark - nice workaround....
> > > and note, be sure to mention this bug to that little programmer that
Omega
> > > hired
> > > to fix TS2000i bugs.
> > > He currently is reviewing line-by-line all estimated 1 million lines
of
> >code
> > > in TS2000i.
> > > Maybe he can find this one.
> > > Maybe not.
> > >
> > > Anyone betting ?
> > >
> > > > -----Original Message-----
> > > > From: Mark Baze [mailto:mark_baze@xxxxxxxxx]
> > > > Sent: Wednesday, August 01, 2001 11:59 AM
> > > > To: omega-list@xxxxxxxxxx
> > > > Subject: Addendum: "New Orders" dialog box problem
> > > >
> > > >
> > > > Regarding my previous post about only a single "New
> > > > Orders" dialog box appearing even though the
> > > > EasyLanguage code contains *both* a protective stop
> > > > and a target limit order to be placed, as I'm watching
> > > > now in realtime, I forgot that there is an even worse
> > > > problem:
> > > >
> > > > When an entry order signal is generated, e.g., from a
> > > > market order to buy at close, initially 3 dialog boxes
> > > > appear, one saying place a Market Order, one saying
> > > > you now have an Open Position, and one saying that
> > > > your order has been Filled. The single protective
> > > > stop dialog box that I was referring to earlier
> > > > actually does not appear until the close of the
> > > > *subsequent* bar. Further, *neither* the protective
> > > > stop order nor the target limit order are sent to the
> > > > Tracking Center until the close of that subsequent
> > > > bar.
> > > >
> > > > Thus, for example, if one is working off of 15 min
> > > > bars, it takes an additional 15 min after generation
> > > > of the entry signal for the single dialog box with the
> > > > stop order to appear and (worse) for the stop and
> > > > limit orders to appear in the Tracking Center.
> > > > Fifteen minutes is a lifetime in futures trading.
> > > >
> > > > As a workaround, I write into the code language to
> > > > have the stop and limit values immediately displayed
> > > > as text on the screen beside the entry bar.
> > > >
> > > > Is this what other people have to do as well or do I
> > > > not have something set correctly so that the stop and
> > > > limit information is sent immediately to the Tracking
> > > > Center?
> > > >
> > > > Thanks again,
> > > > Mark
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
>
|