|
PureBytes Links
Trading Reference Links
|
Everyone knows that they are cheap hire who merely search for the
problems to your questions on a database.
You come up with an idea and work with it. Suddenly, you realize that the TRAD
platform has limitations, even though what they touted seemed to
ring with your idea.
In a fret, you call tech support. Yes, they can in fact tie their own
shoes. But going beyond reading static database scripts requires more
pay, and knowledge pertaining to anything they are
helping you with. So, giving up on that, you rant on their wish
list, hoping that their next version next year will solve all your
trading needs. So you wait and wait and wait.....
Hope your money doesn't run out while you wait....
Thursday, May 22, 2003, 7:03:21 PM, you wrote:
MS> No problem...and thanks......
MS> it's just such a shame that TRAD themselves are so incompetent technically
MS> and can't answer or address these important indicator timing issues.
>> -----Original Message-----
>> From: david b. stanley [mailto:davestan@xxxxxxxxxx]
>> Sent: Thursday, May 22, 2003 11:27 PM
>> To: mar.ko@xxxxxxxxxxx
>> Subject: Re: using pushpop.dll in a strategy/system, clarification.
>>
>>
>> He goes on to say in the manual, that you can test this
>> for yourself using example 16.
>>
>> I never had a reason to send info between indicators and
>> systems however, I have sent information between systems
>> and the order holds true.
>>
>> The necessary file reading and writing required to use global
>> variables on independent windows is too cludgy for me so
>> I stay away from it.
>>
>> I seem to remember years ago on this list, that Kim Horn, the
>> developer of Hashnums had mentioned that he came by his
>> conclusions by trial and error but tested them extensively.
>>
>> sorry I can't confirm the validity for you.
>>
>> Example 16
>>
>> Here is one system and two indicators to test the real time
>> verses historical
>> order things run in. Try inserting them into a chart in different
>> orders. Choose
>> a 1 Minute Bar. You may write your own paintbar and showme along
>> these lines to
>> test them also. You can see the first one to update the Current
>> Bar stored in
>> the DLL. This property can be used to cache a calculated value.
>> If all three
>> check if the current bar is equal to the stored bar value then
>> one only needs to
>> update the calculation when the current Bar is not equal to the stored bar
>> number. You may place this into a function and call it from all of them.
>>
>> {System - 1}
>>
>> DefineDllFunc: "c:\omega\prog\hashnums.dll", INT, "putAt",
>> LPSTR, LPSTR, FLOAT;
>>
>> DefineDllFunc: "c:\omega\prog\hashnums.dll", FLOAT, "getAt",
>> LPSTR, LPSTR;
>> DefineDllFunc: "c:\omega\prog\hashnums.dll", FLOAT, "cleanUp";
>>
>> Variable: CBar(0);
>>
>> CBar = getAt("Test", "CBar");
>> print("System-1: ", CurrentBar, CBar);
>> putAt("Test", "CBar", CurrentBar);
>>
>> { Indicator 1 }
>>
>> DefineDllFunc: "c:\omega\prog\hashnums.dll", INT, "putAt",
>> LPSTR, LPSTR, FLOAT;
>>
>> DefineDllFunc: "c:\omega\prog\hashnums.dll", FLOAT, "getAt",
>> LPSTR, LPSTR;
>> DefineDllFunc: "c:\omega\prog\hashnums.dll", FLOAT, "cleanUp";
>>
>> Variable: CBar(0);
>>
>> Plot1(Open,"Open");
>>
>> CBar = getAt("Test", "CBar");
>> print("Indic-1: ", CurrentBar, CBar);
>> putAt("Test", "CBar", CurrentBar);
>>
>> { Indicator 2 }
>>
>> DefineDllFunc: "c:\omega\prog\hashnums.dll", INT, "putAt",
>> LPSTR, LPSTR, FLOAT;
>>
>> DefineDllFunc: "c:\omega\prog\hashnums.dll", FLOAT, "getAt",
>> LPSTR, LPSTR;
>> DefineDllFunc: "c:\omega\prog\hashnums.dll", FLOAT, "cleanUp";
>>
>> Variable: CBar(0);
>>
>> Plot1(Open,"Open");
>>
>> CBar = getAt("Test", "CBar");
>> print("Indic-2: ", CurrentBar, CBar);
>> putAt("Test", "CBar", CurrentBar);
>>
>>
>>
>>
>>
|