[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Returning Last Signal Name...



PureBytes Links

Trading Reference Links


I didn't see those posts, but thanks.  Why go through the hassle of writing
a com compliant app when you could spend about 1-2 hours writing EL
functions that would do much the same thing?  I was just wondering if there
was an easier way to do it, but looks like I'll just use flags.

> -----Original Message-----
> From: M. Simms [mailto:prosys@xxxxxxxxxxxxxxxx]
> Sent: Thursday, November 02, 2000 8:47 AM
> To: orcas@xxxxxxxx; List, Omega
> Subject: RE: Returning Last Signal Name...
>
>
> No, No, and NO.
> See previous posts where we:
> 1) beat this to death
> 2) contacted Omega tech support and they said "No" and hinted that it will
> NEVER "be in there".
> 3) determined the solution is via a COM compliant DLL estimated to take
> between 40 and 80 hours of programmer time to create, debug and test.
>
> Care to foot the bill ?
>
>
> > -----Original Message-----
> > From: Brian [mailto:blink64@xxxxxxxx]
> > Sent: Thursday, November 02, 2000 12:36 AM
> > To: List, Omega
> > Subject: EL: Returning Last Signal Name...
> >
> >
> > Is there a command in EL that will return the signal of the current open
> > position?  Is there one that can reference names of past signals such as
> > PositionEntrySignal(1) where 1 refers to the the next to last
> entry signal
> > name. (By entry signal name, I'm referring to the "S1" in this statement
> > Sell ("S1") On Close.)  I'm trying to detect, within the system
> code, what
> > signal was last executed without adding my own flags.
> >
> > Thanks,
> > Brian.
> >
> >
>
>