Yes, you should be able to reverse-engineer the math so you could say "when price reaches X, then TMA will be Y." You could use that if you wanted to place a stop entry at the price where TMA would hit X. Of course price might touch X, hitting your entry, and then reverse -- so on an end-of-candle basis the TMA never would have hit Y, but that might be an acceptable risk.mobthehop wrote:was puzzling about this.... Given the calculation of GetSlope based on TMACalc, we should be able to come up with a calculation on what pip movement is necessary to move a given tf's slope by 0.1 - a bit beyond my math skills but should be possible....
Yes, looks like it. GetSlope() gets called twice, both times with a shift of 0. But that's appropriate for an EA, since it's always looking only at the current candle, which is candle 0.Also, could you have a look at the TMACalc / Getslope calculation - the integer shift is not really used as a variable, it is always zero and then shifted in a couple of places, isn't it?