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

Re: Multiple Dll calls....



PureBytes Links

Trading Reference Links

Look at it this way:
You define a dll call for instance "INIT" being in m2002x1.dll.
However you redefine that same call being in m2002x2.dll

You can not do that TS will only use one of the dll's.
To do this you would need 2 EL source files where each source defines only 1
DLL!
Good luck
Robert

ps. One of the reason I don't consider John's software anymore is all this
"messing around" with duplicate DLL's. It doesn't have to be that way but he
doesn't do the effort to do it better.
===============================
Robert Linders
Orlando, FL
email: mugsnug@xxxxxxxxx
===============================
----- Original Message -----
From: "LPrice" <lprice1023@xxxxxxxxxxxxx>
To: <omega-list@xxxxxxxxxx>
Sent: Wednesday, January 30, 2002 11:12 AM
Subject: Multiple Dll calls....


> We are using the Mesa Dll's.  It is our understanding that it is
> possible to call a cycle measurement on two different data streams in a
> TS Strategy by renaming the Dll files.  However our results suggest that
> we are merely calling the same Dll rather than the two separate Dll's.
>
> Here is a sample indicator that we are using.  Could anyone give us some
> suggestions?  The Mesa manual is very vague on this point and when we
> spoke to Mr. Ehlers, he said that he would not consult on system
> development.
> Thank you very much,
> Lawrence Price
>
>
> {DomTest -- Test use of 2 Dominant Cycle calcs in one indicator: Data2
> is a 120-minute bar of any stock,
>      and data3 is the $TICK data.}
>
>
>      Variables: TK(5), Smooth(0), dc1(0), dc2(0);
>
>
>      {-------------------------- Mesa DLL setup
> --------------------------------}
>      defineDllFunc: "c:\mesadll\m2002x1.dll",int,"INIT",int;
>      defineDllFunc: "c:\mesadll\m2002x1.dll",int,"MATRIX",lpstr;
>      defineDllFunc: "c:\mesadll\m2002x1.dll",int,"DomCycle",int, float,
> float, float, lpfloat;
>      defineDllFunc: "c:\mesadll\m2002x1.dll",int,"FindPhase",lpfloat;
>      defineDllFunc: "c:\mesadll\m2002x1.dll",int,"FindTrend",lpfloat,
> lpfloat;
>      defineDllFunc: "c:\mesadll\m2002x1.dll",int,"FindMode";
>
>      defineDllFunc: "c:\mesadll\m2002x2.dll",int,"INIT",int;
>      defineDllFunc: "c:\mesadll\m2002x2.dll",int,"MATRIX",lpstr;
>      defineDllFunc: "c:\mesadll\m2002x2.dll",int,"DomCycle",int, float,
> float, float, lpfloat;
>      defineDllFunc: "c:\mesadll\m2002x2.dll",int,"FindPhase",lpfloat;
>      defineDllFunc: "c:\mesadll\m2002x2.dll",int,"FindTrend",lpfloat,
> lpfloat;
>      defineDllFunc: "c:\mesadll\m2002x2.dll",int,"FindMode";
>
>
>      If currentbar = 1 then begin
>         Init(1);
>         Matrix("XXXXXXXX");
>      End;
>
>      {First DomCycle operates on data2, i.e. stock 120-minute bars}
>      DomCycle(1, close of data2, H, L, &dc1);
>
>
>      {Second DomCycle operates on data3, a smoothed $Tick data3 stream
> biased by +2000
>      for a positive number}
>      TK=(close of data3)+2000;
>      Smooth = AverageFC(TK, 5);
>      DomCycle(1, Smooth, H, L, &dc2);
>
>
>      Plot1(dc1,"dc1");
>      Plot2(dc2,"dc2");
>
>
>