Indicators: T3 floating levels (2)
Thanks you for new indicator!
Hi Mladen,
Thanks you for new indicator!
I don't see any such issue. They use as little resources as possible (you can not calculate t3 with less resources in a meaningful way) and as far as calculation is concerned, tested that version and the initial calculation for 10.000 bars takes less than 1 millisecond
Here is a very simple test expert typed up in order to test the above indicator, and when you run it you shall see that it does not cause any slowdown (neither in visual nor in non-visual testing mode)
input string inpIndicatorPath = ""; // Indicator path (if not in default folder)) input double T3Period = 25; // T3 period input double T3Hot = 0.7; // T3 volume factor enum enT3Type { t3_tillson = (int)true, // Tim Tillson way of calculation t3_fulksmat = (int)false, // Fulks/Matulich way of calculation }; input enT3Type T3Original = t3_fulksmat; // T3 calculation mode input ENUM_APPLIED_PRICE T3Price = PRICE_CLOSE; // Average price enum chgColor { chg_onSlope, // change color on slope change chg_onLevel, // Change color on outer levels cross chg_onMiddle // Change color on middle level cross }; input chgColor ColorOn = chg_onLevel; // Color change on : input int FlPeriod = 25; // Period for finding floating levels input double FlUp = 90; // Upper level % input double FlDown = 10; // Lower level % //------------------------------------------------------------------ // //------------------------------------------------------------------ // // // int _t3Handle; void OnInit() { _t3Handle = iCustom(_Symbol,_Period,inpIndicatorPath+"T3 floating levels (2)",T3Period,T3Hot,T3Original,T3Price,ColorOn,FlPeriod,FlUp,FlDown); } // // // void OnTick() { static datetime _lastChangedAt = 0; // // // double _values[]; double _valuesCopied = CopyBuffer(_t3Handle,4,0,3,_values); if (_valuesCopied==3) { if (_values[0]!=_values[1] && _values[1]!=0 && _lastChangedAt!=iTime(_Symbol,_Period,1)) { Comment(StringFormat("trend changed at %s to %s",TimeToString(TimeCurrent(),TIME_DATE|TIME_MINUTES),(_values[1]==1?"up":"down"))); _lastChangedAt = iTime(_Symbol,_Period,1); } } return; }PS: the copy buffer was used on each tick on purpose in this example (just to make sure that there is no slowdown from the call). That can be easily further optimized (to reduce when the copy buffer was used, since I am testing first closed bar there)
You demand?
For demands please check here : https://www.mql5.com/en/job
- 2021.04.29
- www.mql5.com
This is fixed here: https://www.forexfactory.com/thread/post/14170745#post14170745

T3 floating levels (2):
Updated T3 floating levels
Author: Mladen Rakic