Why won't this work? Please Help! (Color Changing TMA Slope)

Quoting jmflukeiii

Disliked

{quote} I don't have that arrow that you used in my fonts. I have Webdings, Wingdings, Wingdings 2, Wingdings 3. Which did yours come from?

Ignored

Quoting Xaphod

Disliked

{quote} http://docs.mql4.com/constants/wingdings possibly codes 217, 218

Ignored

Quoting jmflukeiii

Disliked

{quote} It is those, but I thought I had to use Wingdings as a font, and not use it throug arrow codes (so I can place it on the chart without having to use time and price coordinates).

Ignored

//+------------------------------------------------------------------+
//| script program start function                                    |
//+------------------------------------------------------------------+
int start() {
  static string sObjName="MyArrow";

  // Create text object
  if (ObjectFind( sObjName)<0) {
      ObjectCreate(sObjName, OBJ_LABEL, 1, 0, 0, 0, 0);
      ObjectSet(sObjName, OBJPROP_CORNER, 1);       
      ObjectSet(sObjName, OBJPROP_BACK, false);
  }

  // Draw text object
  ObjectSet(sObjName, OBJPROP_XDISTANCE,10);
  ObjectSet(sObjName,OBJPROP_YDISTANCE,10);
  ObjectSetText(sObjName, CharToStr(217), 12, "WingDings", Red);

  return(0);
}

Quoting jmflukeiii

Disliked

One of the features of my indicator is going to be telling me the distance to the outer TMA band. The piece of code I am missing in this is to convert pip values from vaious currencies to the same number of decimals. For example, putting the indicator on UJ, subtracting the current Close from the Upper Band will yield a number around .05-.15. Doing the same on EU will yield .0005 - .0015. What is the best way to efficiently transform each of those decimals to X pips, in this case 5 - 15 pips. Thank you

Ignored

Quoting Kilian19

Disliked

{quote} might be helpfull MarketInfo("XXXYYY",MODE_POINT); x*10^Digit = x/Point

Ignored

Quoting jmflukeiii

Disliked

Is there anything similar to Ninja's "Calculate on Bar Close" function, meaning an indicator doesn't print, or calculate, until the bar has closed? Or could you give me another hint in how to deal with the original slope indicator question I had - the holes are filled now when it goes from rising to falling, but its printing both buffers at the turning points... sorry again if this is very elementary, I'm just not seeing how to over come that... [the picture is referencing the aqua and magenta colored line] {image}

Ignored

Quoting Kilian19

Disliked

{quote} Non such function exist but we can easily write our own. You can limit your for loop to not look at the 0 bar which is the most current one and you have to take a look at the indicator counted call. (something like indicator counter + or - 1). Please upload the current indicator so I can see what is causing the issue.

Ignored

Quoting jmflukeiii

Disliked

Is there anything similar to Ninja's "Calculate on Bar Close" function, meaning an indicator doesn't print, or calculate, until the bar has closed? Or could you give me another hint in how to deal with the original slope indicator question I had - the holes are filled now when it goes from rising to falling, but its printing both buffers at the turning points... sorry again if this is very elementary, I'm just not seeing how to over come that... [the picture is referencing the aqua and magenta colored line] {image}

Ignored

int start() {
    static datetime tPrevTime=0;
    
    // usual indicator counted stuff here
    // ...
    
    // Usual loop processing of bars
    for (int i=limit; i>=0; i--) {
       // New bar check
       if (Time>tPrevTime) {
          tPrevTime=Time;
          // Do new bar stuff
          //...
       }
      // the rest of the stuff
      //...
   return(0);
}

Quoting jmflukeiii

Disliked

Thank you both for your replies - Kilian - it only occurs when on new bars being processed . If you load the indicator, or reload it, it will appear perfect. But when using in real time, at the turning points where before we had holes, it will print both buffers.

Ignored

Quote

Disliked

#6
Once you have that fixed the historic bars should be correct. But think about what happens when the current bar is close to the threshold and will be above and below 0 during the same bar? What values will be stored...

Quote

Disliked

EDIT: setting it to calculate only when the bar has closed appears to solve the problem. However, I just don't understand why it doesn't work when it is calculating/updating on the current bar. It should be simple enough -

Quoting jmflukeiii

Disliked

Kilian - that does not work. It makes holes in the plot at the turning points.

Ignored

Quoting Kilian19

Disliked

{quote} Yes at the turning point but that shouldn't be the problem anyways I thought the problem is the bar after the turning point at the turning point both values have to be plotted, thats why we put that code in in the first place! At least that's what I guessed. I haven't had time to look at the indicator today.

Ignored