I will code your EAs and Indicators for no charge

Quoting hdn

Disliked

{quote} I am trying to check it But I do not know the theory of calculations. It is very difficult to solve this problem. However, I will look at it again. Are you Iranian? The phrase "Kheli mutshakaram!!" sounds Iranian.

Ignored

Quoting acetrader

Disliked

{quote} You're welcome & thank you my friend.

Ignored

Quoting hdn

Disliked

{quote} Hello to all my dear friends. I was on a short recreational trip for the past three days. I am currently working on this request. {quote} As soon as this request is finished, I will announce it here and I will answer all the unanswered posts in order. Thank you for your patience and attention. HDN

Ignored

Quoting hdn

Disliked

{quote} Hello to all my dear friends. I was on a short recreational trip for the past three days. I am currently working on this request. {quote} As soon as this request is finished, I will announce it here and I will answer all the unanswered posts in order. Thank you for your patience and attention. HDN

Ignored

Quoting Hunter74

Disliked

Can this have an auto refresh added for an look back x candles to form the zones and remove old ones from the chart automatically??{file}

Ignored

Quoting nomanm47

Disliked

Hello Coders What’s the best way to apply security to an indicator so that it cannot easily be shared around easily? free options or paid (small fee) Im trying to avoid linking account numbers since people are protective over their live account numbers etc. thanks

Ignored

input string Password;
 
int OnInit()
{
 if (Password!= "your_password")
  {
   Alert ("Wrong Password");
    return(INIT_FAILED);
  }
 
  return (INIT_SUCCEEDED);  
}

Quoting olwethufx

Disliked

{quote} hello dear coders. please some help to clean up the code on these indicators, or recode them in MQL4 format. Picked it up on tradingview, apperantly the coding is called pine script, it is opensource. See below. {file} {file} {image}

Ignored

Quoting venkateshr56

Disliked

[/code]{quote} Write code for password input string Password; int OnInit() { if (Password!= "your_password") { Alert ("Wrong Password"); return(INIT_FAILED); } return (INIT_SUCCEEDED); }

Ignored

Quoting T4Trade

Disliked

{quote} these indicators are not working,any reason?

Ignored

Quoting nomanm47

Disliked

{quote} Hi - Thanks for the reply but not quite sure this would work since password can be passed on. Example. I give the indicator to "person A" with the indicator password. Per A can then easily give to "Person B" and tell them the password. So there is no security for me in this being illegally passed around. Thanks

Ignored

Quoting nomanm47

Disliked

Hello Coders What’s the best way to apply security to an indicator so that it cannot easily be shared around easily? free options or paid (small fee) Im trying to avoid linking account numbers since people are protective over their live account numbers etc. thanks

Ignored

Quoting jeanlouie

Disliked

{quote} Here it is; Cur_Prev_Day-Week-Month_Candles_v1.4 - added ability to have 2 instances of the indicator at the same time, for each current-previous setting (ie 2 instances max) - note remember to space them differently too via the bar offset option for each day-week-month candle. The pic has the current candles at default positions, the previous is set ...I think I had them at day-74, wk-84, mn-94 bar offsets, to take a pic of both instances at the same time {image} {file}

Ignored

Quoting nomanm47

Disliked

Hello Coders What’s the best way to apply security to an indicator so that it cannot easily be shared around easily? free options or paid (small fee) Im trying to avoid linking account numbers since people are protective over their live account numbers etc. thanks

Ignored

Quoting Georgebaker

Disliked

{quote} You can try this - See if you like it https://www.youtube.com/watch?v=wTNbiBWMPCE&t=641s

Ignored

#define LIC_PRIVATE_KEY
#define LIC_PRIVATE_KEY_ACCT_LAST_NUMCHAR 3   // 3 or 2 suggested
 
#ifdef LIC_PRIVATE_KEY
   //long  account  =  AccountInfoInteger(ACCOUNT_LOGIN);
   string account_str = IntegerToString(AccountInfoInteger(ACCOUNT_LOGIN));
   #ifdef LIC_PRIVATE_KEY_ACCT_LAST_NUMCHAR
      account_str = StringSubstr(account_str, StringLen(account_str)-LIC_PRIVATE_KEY_ACCT_LAST_NUMCHAR);
   #endif
   Print("DEBUG Looking for account_str=",account_str);  // Comment out after you're comfortable with my changes.
   string result  =  KeyGen(account_str, LIC_PRIVATE_KEY);
   if (result!=licence) {
      Print("Invalid licence");
      return(false);
#endif
 
// The KeyGen() code is in the video

Quoting pips4life

Disliked

{quote} This video posted by Georgebaker was very helpful to me (Thanks George!) : {quote} However, since it still relies upon the full account number, it's not yet a solution for you. (I too am reluctant to disclose complete live account info to others, though the actual risk is probably small). As a solution, I would suggest you could use a partial account number as the matching key, say, just the last 2 or 3 digits would be enough. (One of my live accounts is just 6 digits, and the 1st 3 are easily guessed within a narrow range of possibilities)....

Ignored