|
PureBytes Links
Trading Reference Links
|
I believe you get one DLL instance per instance of TradeStation. I'm not a
Windows expert, but generally shared libraries are loaded into the
applications memory space and you get one per app. You can use this to
your advantage in that you can share memory between all of your EL code no
matter where it is applied in TS.
It's been a while since I've worked with this code (I have infrastructure
in place that handles it in the background now), but basically when you
add/remove indicators that reference your DLL, TradeStation automatically
invokes pre-defined functions in your DLL (that you can implement) that it
passes unique IDs in to. You can use these ID's to "map" to your static
memory.
The functions of interest are DLL_Add(id) (when indicators are added),
DLL_Remove(id) (when indicators are removed / turned off), DLL_Context(id)
(called immediately before any of your functions so you can determine which
EL indicator is calling).
At 07:25 PM 3/13/2001 -0500, Bilo Selhi wrote:
>does anyone have a sure answer for the following quetion:
>
>when tradestaion loads a custom dll does it tie that dll instance
>to a chart object or to a study object ( system or indicator ) within the
>chart?
>
>in other words...
>if i have one chart open and i load a system that calls mylib.dll and
>in the same chart i load an idicator that also calls mylib.dll ...
>does tradestion allocate memory for that dll per chart or per
>study? one dll instance ( per chart ) or two separate dll instances
>one per each study loaded in the chart???
>
>thank you.
>bilo.
---
Yahoo account: david_wieringa
Software Engineer (contractor)
Scottsdale, AZ / Grand Rapids, MI
|