Page 1 of 1

ERG Logic Autolabeling: trouble with text => reason FOUND

Posted: Mar 16 2006
by swisstrader
I could find out the reason for it:

1. It isn't a problem with TextID!!!!
2. In my code is at the beginning of a subroutine a trigger to go into this subroutine. If this trigger = TRUE, so at first I move my values in the array like a slide-register (FIFO). BUT: the trigger is reacting on BOTH chart bars: one time at 49 sb and second time at 343 that my slide-register is moving TWO TIMES and saves TWO TIMES in a row the same calculated value. The comparison MUST give an MATCH-PPF.

Problem fixing: the tool which runs corresponding under in Format Study => Properties => Study base on: 2. @EC 49 share bars chosen setting shall not trigger on both bar charts, only on chart 2. That is to fix in MC platform OS.

After I have inserted an self-lock for this subroutine my tool works now fine in a multi timeframe chart. But this is an interim solution until the bug fixing.

-swisstrader

little advertisement for my tool ...

Posted: Mar 16 2006
by swisstrader
this tool also is showing MINOR and PRIME oscillations with 2x and 3x divergences and 2x, 3x reverse divergences

:D

Posted: Mar 17 2006
by Alex Kramer
Thanks, I showed this to the developers.

Posted: Mar 21 2006
by Alex Kramer
This will be fixed in the next version, so I was assured by the developers.

Posted: Mar 21 2006
by swisstrader
I have tried to repair it in my code and I have changed all 'CLOSE' to the equivalent datastreams.

But now is nothing to see. No plot, no label ...

see also at thread
http://forum.tssupport.com/viewtopic.php?t=792

Posted: Mar 24 2006
by swisstrader
reason was found, see the first post of this threah, I've changed it.

Posted: Mar 24 2006
by Alex Kramer
Good to hear, but one question:

>Problem fixing: the tool which runs corresponding under in Format Study => >Properties => Study base on: 2. @EC 49 share bars chosen setting shall not >trigger on both bar charts, only on chart 2. That is to fix in MC platform OS.

How does TS platform handle this - the way you do it now and expect MC to do? If so, please tell what build of TS is that?
If you could send a simple example of your indicator where the issue is reproduced (no need for your complete proprietary indicator), this will clear the situation at once and forever.