Thanks jcl & DdlV,
I'm understanding!
DdlV, on this one piece:
No, per the manual, the tmf is called every tick, not only at the time of trade entry.
Also per the manual, these parameters are passed again with each call, so each call will use their current values.
...my findings are different. What I meant in my above statement was that the TMF is only triggered upon trade entry.
My finding is that a changing value cannot be re-sent as an argument to the tmf() via enterLong(). For example, if you wanted to send the current value of a custom series you built within the run() function (which is different on each iteration of run() )
(Sidenote: for lack of better terminology, the way I envision Zorro working is that a tmf() is essentially "spawned" from the run() loop. Whereas run() loops once per BarPeriod, tmf() loops once per tick. Therefore, the loops run independently and simultaneously. As such, once the tmf() is spawned, it would not be re-spawned again for that trade, which explains why no further arguments can be sent via the initiation.)
Instead, you can set TradeVar[0] in the run() function with your changing series value, and it will be accessible within the tmf() that is already active. That would allow one-per-BarPeriod current value to be accessible within the tmf()
Those are my findings at least. If this is not correct in any way please clarify. Thanks
