Elite indicators :) - page 705

 
traderduke:
malden

Here is nmc problem. Do they "mql" have a syntax book written YET!

Thanks

Ray

Ray

No syntax book (yet). As far as I know Renat told that there will be no updated book (if I remember correctly, what he told was something like "mql has no intention whatsoever to update the existing book to new coding rules")

Anyway, here you go : ml-heiken_ashi_zone_trade_histo_nmc.mq4

 

Updated color stochastic : color_stochastic__mtf_nmc.mq4

Originally (with detailed description) it was posted here : https://www.mql5.com/en/forum/general

 

...

This is the multi time frame version of the color stochastic posted a few posts before

As far as I see all mtf possible issues are solved.

___________________________

A couple of things that might need and explanation upfront.

Arrows are drawn on the first bar of the chosen time frame. In reality it might not be so : the arrow might have happened on any of the bars belonging to the chosen time frame (for example if you are on a 5 minute chart and watching 1 hour time frame, the arrow is drawn at nn:00 while the arrow actually could have happened on any of the 12 bars (from nn:00 to nn:55 minutes) belonging to that 1 hour bar) It was a matter of scoice : either I draw an arrow on every bar belonging to the target bar or I draw just one. I chose the simpler solution (not coding wise, but visually : there would be zillion arrows otherwise)

What I told, non repainting can be a drag in multi time frame but this one has that issue solved : here is a comparison what I was talking about - upper is the new one (interpolate set to false for comparison sake) and lower is the "old" one (the v1.04d). Even though they are not "coloring" the same thing, it is obvious where the problem is and which version works as it should

And the last : alerts are triggered once per target time frame bar. So, if you are watching 1 hour time frame on a 5 minute chart, you will get an allert only once in an hour and not 12 times (for every 5 minute bar belonging to that target 1 hour bar)

That is all. As usual, you can choose to interpolate or not and then they look like these :

PS: for cases when you wish to place more than one indicator on a same chart, supply unique name for arrows in the arrowsIdentifier parameter. That way they will not "mix" arrows (arrows are objects it this indicator, and they need unique names in order to be managed properly - automatic unique name generation does not work in cases of metatrader crashes or templates, hence I do not use the automatic unique name generation)

_______________________

Updated version posted here : https://www.mql5.com/en/forum/general

 
A bit upgraded indicator from this post Stochastic Oscillator : all sorts of alerts added and a bit different way how multi time frame can be treated : dss_of_adaptive_smoother_2.mq4
 

Updated tvi : tvi_nmc.mq4

Originally it was posted here : https://www.mql5.com/en/forum/general

Files:
tvi.gif  59 kb
tvi_nmc.mq4  6 kb
 

...

casaliss

Multi time frame TVI (rewritten completely - results are the same) Renamed it too to just TVI , since there is nothing related to "ticks" in its calculation (best description would be a "kind of a double smoothed volume modified close to open momentum calculation")

Updated version posted here : https://www.mql5.com/en/forum/general

regards

mladen

casaliss:
Hi Mladen

MTF

Thanks
Files:
tvi.gif  21 kb
tvi.mq4  6 kb
 

Updated super trend (non-repainting version) : supertrend_nrp_nmc.mq4

Originally it was posted here : https://www.mql5.com/en/forum/general

Files:
 

yama

Here you go

___________________

There are some differences, though. The first one is where the super trend line is drawn. In the one you posted there is a part of code that was obviously trying to solve the problem of different time frames (this part of code) :

switch(Period()) {

case 1: UpDownShift = 3; break;

case 5: UpDownShift = 5; break;

case 15: UpDownShift = 7; break;

case 30: UpDownShift = 9; break;

case 60: UpDownShift = 20; break;

case 240: UpDownShift = 35; break;

case 1440: UpDownShift = 40; break;

case 10080: UpDownShift = 100; break;

case 43200: UpDownShift = 120; break;

}

It is, more or less trying to adjust distance in pips for different time frames. The first problem is that it is meant for 4 digit brokers (which is the smaller problem - it is taken care of in this version) and the other is that it makes constant difference regardless of volatility. Even Jason Robinson gave up that way and took what is used in the Atr stops or Jan Arps "original" (the one Jan Arps calls "trender") and uses average true range instead for the distances and not fixed distances. Anyway, I left an option to use "old calculation" which approximates the "old way" (not 100% since I did not want to go entiely back as far as the calculations are concerned)

As a comparison, it does not matter which calculation is used, the color changes are at the same places (it is a CCI trend after all )
Added the usual stuff : interpolation, non repainting ,... Here is a 1 hour super trend on a 15 minute chart. Default CCI length in this one is changed from 14 to 50 (it is more or less common for it, but you can change it in parameters to any length you wish)

___________________

After this lengthy post, I wish you a pleasant weekend

regards

mladen

yama728:
Hi and thanks mladen.

I want to MTF "super trend" indicator please.

sorry my poor english...

thanks

Updated version posted here : https://www.mql5.com/en/forum/general

 

Updated T3 dpo : t3_dpo-v2_nmc.mq4

Originally it was posted here : https://www.mql5.com/en/forum/general

Files:
t3_dpo.gif  66 kb
 

yama,

Here you go Changed it a bit :
Removed the bars limitation (it now calculates the whole history)

Now you can choose the price instead of using the fixed close

You can choose between original Tillson T3 calculation and Fulks / Matulich calculation (T3Original parameter - by default set to Fulks / Matulich since it was the one used in the one you posted)

And the usual stuff for multi time frame
PS: at yamas request made one with arrows and alerts. Attached it here to keep them together

Updated version of T3 dpo posted here : https://www.mql5.com/en/forum/general

regards

mladen

yama728:
Thanks mladen.

its my best indicator:)

look at image file.

Super trend and T3-DPO are best combination.

can adding MTF at T3-DPO?

thanks!
Files:
Reason: