[BlowFish]

Did my suggestion not work? It should have done if the question was correctly expressed in your original post.

Once you trigger true nothing in your code ever resets back to false. Either always reset to false at the start of your code -or- have an else clause where you test your conditions. The former will just show the bar that transitions from false to true the latter will show all bars that meet the condition. Simple logic error.

Problem solved as far as I can see.

[mrtraderguy]

Originally Posted by nab999 »

At Bar A either the fast or the slow average have a slope that is either down or level.

At Bar B the slope of both the fast and slow averages are up, so on this bar the show me plot would be made.

No further plots are made until a new bar A followed by a new bar B formation is made.

A) OK, so the setup (assuming TS 8.6) is a symbol with at least three data series:
[1]Symbol, [2] Slow Stochs, [3] Fast Stochs.
--> Note: I do expect the data series to be in the right place; I don't error check on this since I write stuff for myself and keep all my setups correct by hand :-)

B) So you're looking for divergence between data series [2] & [3] then, from what I read above.

C) The main condition is that both lines in [2] are flat or down and both lines in [3] are up.

D) Crossing of the lines is not relevant here; just [2] both flat/down and [3] up at the same time.

E) The processing of the conditions does not occur intra-bar, only on closed bars.

Is this correct? I'm rebuilding some code now that was lost during a BlueScreen this morning, so since most of this is the same as what I have, I'll post what I have later and you can use it if you want or can change it to whatever you need.

MTG

[Tams]

Originally Posted by BlowFish »

Did my suggestion not work? It should have done if the question was correctly expressed in your original post.

Once you trigger true nothing in your code ever resets back to false. Either always reset to false at the start of your code -or- have an else clause where you test your conditions. The former will just show the bar that transitions from false to true the latter will show all bars that meet the condition. Simple logic error.

that's why I insist on people writing out their thoughts,
instead of jumping into coding immediately.

Originally Posted by BlowFish »

Problem solved as far as I can see.

I really don't care if he solved the problem...
some people only want a quick fix. As far as I am concerned, the "problem" is not in the logic.

[BlowFish]

Thats not what he said Mr T G, he simply wants a mark when two moving avergaes ( a fast and a slow) both turn up. Single data series, no stochs, no divergences, unless I mis read the original post and code.

this will probably do it though I have simply modified your original code so might not be the most elegant way of doing it.

inputs:
fastLength(5),
slowLength(10),
BEx(0.5);

Var:
longTrigger(false),
longTriggerValue(0),
fastValue(0),
slowValue(0);

longTrigger = false;
Value1=LOW ;

fastValue = Average( Close, fastLength );
slowValue = Average( Close, slowLength );

if fastvalue[1]<=fastvalue[2] or slowValue[1] <= slowValue[2] then {where previous MA's down?}
  If FastValue>FastValue[1] and slowvalue>slowvalue[1]               {if so check if current MA is up}
     and close>open then longTrigger = true;


if longTrigger=true then
begin
  longTriggerValue = High +( range * BEx );

  Plot1(Value1);
  Plot2(LongTriggerValue);
end;

Cant remember whether braces are EL comments or a MC extension might have to change those.

[BlowFish]

Originally Posted by Tams »

that's why I insist on people writing out their thoughts,
instead of jumping into coding immediately.

I really don't care if he solved the problem...
some people only want a quick fix. As far as I am concerned, the "problem" is not in the logic.

Actually that was why I tried to help compared t0o many posters he did a reasonable job of describing what he was trying to do . He posted some code that he had taken a stab at, reasonably clearly described what he was trying to do and posted a chart with an illustration of how it looked and how it should look. Compared to many of the "please help" posts a zillion miles ahead ! I think (though I may be mistaken) there was enough information in the original post to provide a solution. Time will tell I guess!

Having said that your advice was spot on for him finding the solution for himself.

[mrtraderguy]

I agree with you both, (BFish/Tams) ... it could be just a quick fix need, but I don't really like to try to do quick-fix as it always seems to effect other things and make other problems.

Start simple, test, expand, test, etc. is my motto :-)

Anyway, since I have a similar indicator, just offering to share/help as best I can; not necessarily fix anything existing ... just giving back what I can as I get help from time-to-time as well. I'm not claiming anyone, myself included, right or wrong; just providing options :-)

[Tams]

the problem is...
most wishful thinkers write in mumble jumbles...


writing out their fantasy is easy,
but until people can write out their "wishes" one thought/one line at a time...
the codes will be mumble jumble too.

I have yet to be proven wrong on that.

;-)>

[BlowFish]

Mr T G, You can often learn something new by how others approach problem. There was a great thread "plotting globex highs and lows" or something similar. What was good about it is that several methods to do it where presented, some from fairly novice coders. Anyway reading back my post sounds unduly critical that was not my intention, apologies.