TMA-CG-2024

Quoting BestTraderEv

Disliked

{quote} Please find my tweaks which allow for changing colors and styles: https://www.forexfactory.com/thread/...9#post15013259

Ignored

Quoting jblanked

Disliked

{quote} No, you can fork the repository on Github and submit a pull request. Also, you can already change colors. Download the updated versions from Github, as explained in Post #1.{image} {image}

Ignored

Quoting BestTraderEv

Disliked

{quote} Why do you make things more complicated than they need to be? Just post the whole .zip or .rar file in post one. You can edit post one always.

Ignored

Quoting BestTraderEv

Disliked

@jblanked Why do you dislike my posts? Even when they are useful and helpful?

Ignored

Quoting jblanked

Disliked

{quote} Because I explained to you already to submit your changes on Github.

Ignored

Quoting BestTraderEv

Disliked

{quote} Well, I have never used Github... I don't have an account there. Anyways, your latest version still doesn't work. {image} Maybe it's because there was an MT5 update, just today? I don't know, because I just sat down to check out your versions of this indicator...

Ignored

Quoting jblanked

Disliked

{quote} Its time to create a GitHub account and start learning man. Let me know if you need guidance. You’re getting that error still because of your edits to the source code https://www.forexfactory.com/thread/...9#post15013259

Ignored

Quoting BestTraderEv

Disliked

{quote} No, I did not edit anything in the latest version from Github. The version which I edited works fine.

Ignored

Quoting BestTraderEv

Disliked

{quote} Same with the MT5 version: Ooops, at the moment not working. {image} And that's not my fault! ......... @jblanked: PS. I guess, creating an .mqh file isn't always a good idea, when it can be simple. It looks like trying to set a label for buffer type INDICATOR_CALCULATIONS in MQL5 returns an error and the whole indicator becomes useless.

Ignored

Quoting BestTraderEv

Disliked

{quote} Well, I have never used Github... I don't have an account there. Anyways, your latest version still doesn't work. {image} Maybe it's because there was an MT5 update, just today? I don't know, because I just sat down to check out your versions of this indicator...

Ignored

Quoting Darwati

Disliked

those who compile with meta editor 27 feb 2024 may also experience this, only silent readers usually will be silent too {image} but for me it's no problem because the ex4 file is usable, and I can use other TMA-CG mq4 sources

Ignored

Quoting jblanked

Disliked

{quote} Download the latest version (v1.01) and make sure to download the .mqh file(s) as well; that's why it gave the undeclared identifier warnings.

Ignored

Quoting jblanked

Disliked

{quote} It's your source code. Not only did you edit the initial version, you also removed some crucial components, which is why you're getting those errors. This is your code you posted: https://www.forexfactory.com/thread/...9#post15013259 {image} {image} This is the latest version {image} {image}

Ignored

Quoting Darwati

Disliked

{quote}i usually work with pure custom indicators without mqh or dll files

Ignored

Quoting BestTraderEv

Disliked

{quote} Ooops, sorry, I see what's wrong! However, still, somebody already mentioned it above. When we change the Tf and the dtata needs to download, we get this: {image} And this doesn't change untill we switch Tf's or refresh the indicator.

Ignored

Quoting jblanked

Disliked

{quote} That's understandable brother. However, in other coding communities, using libraries is highly recommended, as it's often considered unprofessional to have thousands of lines of code in a single file. Libraries help organize similar ideas and simplify your workflow, allowing you to develop faster.

Ignored

Quoting jblanked

Disliked

{quote} I'm working on a full solution for that but on the first chart load, MT5 will load the candle history required by indicators. That is why when you load that timeframe a second time, everything is back to normal. In my experience, if you start from the lower timeframes and go up, often the higher timeframe history has already been loaded

Ignored

  if(time[0]<time[iBarShift(_Symbol,PERIOD_CURRENT,TimeCurrent(),false)])
   return(0);

  if(iBarShift(_Symbol,PERIOD_CURRENT,TimeCurrent(),false)!=0)
   return(0);