Need to repair TMA Slope Dashboard

[atharmian]

Hi All,


I am not a coder, so looking for help.

Found a TMA Dashboard below (see pic) from one of the threads and combined it with FF hanover's Recent Strength indy to come up with a dashboard that gives both 28 pairs and the 8 major currency strengths in MTF.

Attaching the mq4s and tpl. [ I just close the Global Market Trend window usually, and it is not relevant to the discussion here.]

FF hanover's RS is based on price change, while the TMA Slope dash arrows are based on the slope of those price changes in a smoothed MA (TMA), as far as I understand. The two different POVs helps in analyzing movements better, but the Arrow Dash could simply also be based on price changes without much loss of information- the Slope by definition would lag a bit behind direct price change display.

This way one can quickly glance at the TMA Arrow Pairs Dash to locate a few weakest/strongest pairs, then look at hanover's RS MTF to confirm various currency strengths. The next step simply will be to go to NB 10.4/10.5 and confirm the MA240 Trend, RS values and suitable pivot/R/S entry. So step by step, one can manually trade pairs with very little time invested...

The problem: While hanover RS works well, the TMA Slope has issues.

1. It only updates based on the TF it is in, e.g., every min in M1. Need to have a menu choice of update interval by tick, M1, and beyond.

2. Is the TMA Slope coding done right here, based on Baluda's latest code? Seems like the Dash doesn't handle more than 4 TFs well, and starts messing up additional TFs. Orginally the Dash I picked from here, and it was missing two of the 28 major pairs, which I added manually:

http://www.stevehopwoodforex.com/phpBB3 ... 481#p14481

3. Also, for some reason, 2-3 random pairs always seem to be in 'neutral' mode, not always because of lack of data, but quite simply not being populated.

4. I patched up 4 instances of the TMA Slope Dash to fit my screen size, 7 pairs visible x 4 columns, while putting up all 28 pairs in each instance. So the CPU load is 4x unnecessarily. Perhaps someone can code one TMA Slope Dash instance with a choice of visible pairs x column = 28.


Can someone(s) help here? Thanks a lot folks !


Athar.