.

Re: Coding Help

#961
Hello Mrtools i need your help please, I trying to use this indicator with iCustom, I need a signal for up and down in current candle when bar apears in subwindows, no signal when no bar, My code work well for put but not for call signals whats wrrong? Thanks soo much in advance.
RSIFilter_v1+.mq4
(5.04 KiB) Downloaded 91 times
Rsi-Filter-Test-1.png
Rsi-Filter-Test-2.png


Re: Coding Help

#962
Cladi39 wrote:
Tue Apr 02, 2019 4:09 am
Hello Mrtools i need your help please, I trying to use this indicator with iCustom, I need a signal for up and down in current candle when bar apears in subwindows, no signal when no bar, My code work well for put but not for call signals whats wrrong? Thanks soo much in advance.
Maybe try something like this for the rsi call function, looks like the rest is ok.

Code: Select all

double upnow = iCustom(NULL,0,"RSIFilter_v1+",PeriodRSI,0,i);
double uppre = iCustom(NULL,0,"RSIFilter_v1+",PeriodRSI,0,i+1);
double dnnow = iCustom(NULL,0,"RSIFilter_v1+",PeriodRSI,0,i);
double dnpre = iCustom(NULL,0,"RSIFilter_v1+",PeriodRSI,0,i+1);

if (upnow!=EMPTY_VALUE  &&  uppre==EMPTY_VALUE && dnnow==EMPTY_VALUE  &&  dnpre==EMPTY_VALUE) return(1);
if (upnow==EMPTY_VALUE  &&  uppre==EMPTY_VALUE && dnnow!=EMPTY_VALUE  &&  dnpre==EMPTY_VALUE) return(-1);

Re: Coding Help

#964
Hello! I really need your help. It is necessary to modify the AllHeikin-Ashi_v2.4.mq4 indicator; it needs to be changed, namely, add various filters and functions to it from other indicators that are attached in the Compressed.zip archive. I'll sign for now.


1) In the AllHeikin-Ashi_v2.4.mq4 indicator, you need to change the code responsible for the MA_Method field so that it does not prescribe a digit from 0 to 26, but choose the type of MA from the drop-down menu according to which a digit is specified in the code from 0 to 26.


2) From the indicator ema variation + filter 3 mtf_edit.mq4
please, copy code correctly:

Code: Select all

enum enPrices

{

pr_close, // Close

pr_open, // Open

pr_high, // High

pr_low, // Low

pr_median, // Median

pr_typical, // Typical

pr_weighted, // Weighted

pr_average, // Average (high+low+open+close)/4

pr_medianb, // Average median body (open+close)/2

pr_tbiased, // Trend biased price

pr_tbiased2, // Trend biased (extreme) price

pr_haclose, // Heiken ashi close

pr_haopen , // Heiken ashi open

pr_hahigh, // Heiken ashi high

pr_halow, // Heiken ashi low

pr_hamedian, // Heiken ashi median

pr_hatypical, // Heiken ashi typical

pr_haweighted, // Heiken ashi weighted

pr_haaverage, // Heiken ashi average

pr_hamedianb, // Heiken ashi median body

pr_hatbiased, // Heiken ashi trend biased price

pr_hatbiased2, // Heiken ashi trend biased (extreme) price

pr_habclose, // Heiken ashi (better formula) close

pr_habopen , // Heiken ashi (better formula) open

pr_habhigh, // Heiken ashi (better formula) high

pr_hablow, // Heiken ashi (better formula) low

pr_habmedian, // Heiken ashi (better formula) median

pr_habtypical, // Heiken ashi (better formula) typical

pr_habweighted,// Heiken ashi (better formula) weighted

pr_habaverage, // Heiken ashi (better formula) average

pr_habmedianb, // Heiken ashi (better formula) median body

pr_habtbiased, // Heiken ashi (better formula) trend biased price

pr_habtbiased2 // Heiken ashi (better formula) trend biased (extreme) price

2.2 If compatible, add this code:

Code: Select all


extern double Divisor = 3; // Divisor to use for "ema" calculation

extern double Filter = 1; // Filter

extern int Precision = 5; // Precision

extern bool Interpolate = true; // Interpolate multi time frame data?

- all that is compatible from this, that it was transferred and worked correctly.

3) From the AMkA.mq4 indicator
copy code correctly:

Code: Select all

"//---- периоды

extern int periodAMA = 9; //период расчёта к-та эффективности

extern double nfast = 2; //период EMA для эффективного рынка

extern double nslow = 30; //период EMA для неэффективного рынка

//---- расчёт сглаживающей константы

extern double Pow = 2.0; //степень эффективности

//---- фильтр сигналов

extern double dK = 1.0; //коэффициент для фильтра

extern bool use_stdev = true; //использовать стандартное отклонение
It is very important that all this does not conflict in the calculations between themselves. Please add what is really added. I want the "top" and "bottom" to be better identified by the indicator. I attach a set (settings file). On M1 I use this indicator with settings from .set. Very grayscale indicator can turn out. Thank you in advance and hope for your help in refining this indicator. If you have a desire and time to help, you will be very happy. All the necessary indicators are a part of the code from which I ask to transfer correctly to AllHeikin-Ashi_v2.4.mq4 in this post in the attachment.

There is also a dream to see an adviser based on the modified AllHeikin-Ashi_v2.4.mq4 indicator.

Advisor skills:

1. As soon as it became aware of the color of the relevant sell transaction (by default it is red color), the sell transaction also opens here, when the color changes to the corresponding purchase (by default it is blue) to close the open sell and open buy.
2. Make it possible not to be tied to color, but to Volume, that is, to give the sell and buy values ​​their identifiers so that there is no dependence on a particular color so that you can change the color without affecting the work of the adviser, so that if you set it to sell black and for buy orange, so that the adviser understands where to buy, and where to sell.
3. So that it was possible to set a trailing stop, martingale on / off, a customizable ability to double the volume of a losing trade by the Martingale method while losing.

I hope for your timely assistance and answers on the subject of the request. All the best, health, good and more money!)
Compressed.zip
(13.77 KiB) Downloaded 58 times

Re: Coding Help

#965
Hi! Can someone help me please?
Created Panel+Button in it, but when i move panel to any corner, panel mooves nice, but Button follows panel on Upper)
Seems like i dont properly inject button in panel / or im not peel off the binding angle of button.


Re: Coding Help

#966
Understanding wrote:
Sun Apr 28, 2019 5:12 am
Hello! I really need your help. It is necessary to modify the AllHeikin-Ashi_v2.4.mq4 indicator; it needs to be changed, namely, add various filters and functions to it from other indicators that are attached in the Compressed.zip archive. I'll sign for now.


1) In the AllHeikin-Ashi_v2.4.mq4 indicator, you need to change the code responsible for the MA_Method field so that it does not prescribe a digit from 0 to 26, but choose the type of MA from the drop-down menu according to which a digit is specified in the code from 0 to 26.


2) From the indicator ema variation + filter 3 mtf_edit.mq4
please, copy code correctly:

Code: Select all

enum enPrices

{

pr_close, // Close

pr_open, // Open

pr_high, // High

pr_low, // Low

pr_median, // Median

pr_typical, // Typical

pr_weighted, // Weighted

pr_average, // Average (high+low+open+close)/4

pr_medianb, // Average median body (open+close)/2

pr_tbiased, // Trend biased price

pr_tbiased2, // Trend biased (extreme) price

pr_haclose, // Heiken ashi close

pr_haopen , // Heiken ashi open

pr_hahigh, // Heiken ashi high

pr_halow, // Heiken ashi low

pr_hamedian, // Heiken ashi median

pr_hatypical, // Heiken ashi typical

pr_haweighted, // Heiken ashi weighted

pr_haaverage, // Heiken ashi average

pr_hamedianb, // Heiken ashi median body

pr_hatbiased, // Heiken ashi trend biased price

pr_hatbiased2, // Heiken ashi trend biased (extreme) price

pr_habclose, // Heiken ashi (better formula) close

pr_habopen , // Heiken ashi (better formula) open

pr_habhigh, // Heiken ashi (better formula) high

pr_hablow, // Heiken ashi (better formula) low

pr_habmedian, // Heiken ashi (better formula) median

pr_habtypical, // Heiken ashi (better formula) typical

pr_habweighted,// Heiken ashi (better formula) weighted

pr_habaverage, // Heiken ashi (better formula) average

pr_habmedianb, // Heiken ashi (better formula) median body

pr_habtbiased, // Heiken ashi (better formula) trend biased price

pr_habtbiased2 // Heiken ashi (better formula) trend biased (extreme) price

2.2 If compatible, add this code:

Code: Select all


extern double Divisor = 3; // Divisor to use for "ema" calculation

extern double Filter = 1; // Filter

extern int Precision = 5; // Precision

extern bool Interpolate = true; // Interpolate multi time frame data?

- all that is compatible from this, that it was transferred and worked correctly.

3) From the AMkA.mq4 indicator
copy code correctly:

Code: Select all

"//---- периоды

extern int periodAMA = 9; //период расчёта к-та эффективности

extern double nfast = 2; //период EMA для эффективного рынка

extern double nslow = 30; //период EMA для неэффективного рынка

//---- расчёт сглаживающей константы

extern double Pow = 2.0; //степень эффективности

//---- фильтр сигналов

extern double dK = 1.0; //коэффициент для фильтра

extern bool use_stdev = true; //использовать стандартное отклонение
It is very important that all this does not conflict in the calculations between themselves. Please add what is really added. I want the "top" and "bottom" to be better identified by the indicator. I attach a set (settings file). On M1 I use this indicator with settings from .set. Very grayscale indicator can turn out. Thank you in advance and hope for your help in refining this indicator. If you have a desire and time to help, you will be very happy. All the necessary indicators are a part of the code from which I ask to transfer correctly to AllHeikin-Ashi_v2.4.mq4 in this post in the attachment.

There is also a dream to see an adviser based on the modified AllHeikin-Ashi_v2.4.mq4 indicator.

Advisor skills:

1. As soon as it became aware of the color of the relevant sell transaction (by default it is red color), the sell transaction also opens here, when the color changes to the corresponding purchase (by default it is blue) to close the open sell and open buy.
2. Make it possible not to be tied to color, but to Volume, that is, to give the sell and buy values ​​their identifiers so that there is no dependence on a particular color so that you can change the color without affecting the work of the adviser, so that if you set it to sell black and for buy orange, so that the adviser understands where to buy, and where to sell.
3. So that it was possible to set a trailing stop, martingale on / off, a customizable ability to double the volume of a losing trade by the Martingale method while losing.

I hope for your timely assistance and answers on the subject of the request. All the best, health, good and more money!)
Have you seen this one viewtopic.php?p=1295198273#p1295198273

Re: Coding Help

#967
MrTools, can you help me please? my question is above a bit.
(Created Panel+Button in it, but when i move panel to any corner, panel mooves nice, but Button follows panel on Upper)
Seems like i dont properly inject button in panel / or im not peel off the binding angle of button.)

Code: Select all

int OnInit()
   {

//--- create application dialog
   RectLabelCreate(0,"RectLabel",0,0,0);
   
   ButtonCreate(0,"button",0,0,0);
   ButtonCreate(0,"button",0,0,0);

   
   
return(INIT_SUCCEEDED);
  }
//+------------------------------------------------------------------+
//| Expert deinitialization function                                 |
//+------------------------------------------------------------------+
void OnDeinit(const int reason)
  {
//---
ObjectDelete (0,"RectLabel");   
ObjectDelete (0,"buttonbuy");   
ObjectDelete (0,"buttonsell");   
  }
//+------------------------------------------------------------------+
//| Expert tick function                                             |
//+------------------------------------------------------------------+
void OnTick()
  {
//---
   
  }
//+------------------------------------------------------------------+
//| ChartEvent function                                              |
//+------------------------------------------------------------------+
void OnChartEvent(const int id,
                  const long &lparam,
                  const double &dparam,
                  const string &sparam)
  {

//---
   int x = (int) ObjectGetInteger(0,"RectLabel",OBJPROP_XDISTANCE);
   int y = (int) ObjectGetInteger(0,"RectLabel",OBJPROP_YDISTANCE);
   
   ObjectSetInteger(0,"button",OBJPROP_XDISTANCE,x);
   ObjectSetInteger(0,"button",OBJPROP_XDISTANCE,y);
   
   if(ObjectGetInteger(0,"button",OBJPROP_STATE)==true);  
  }

Re: Coding Help

#970
traderduke wrote:
Wed May 01, 2019 4:42 am
mrtools
could you add alerts and arrows to this Keltner
thank you
Ray

jurik keltner channel 1.01 mtf.mq4
What conditions do you want the alerts?


  1. Similar Topics

    1. Help coding simple EA

      5 Replies 584 Views

      by Griff90, Tue Nov 13, 2018 8:36 am in Coding Help

      5 Replies
      584 Views
    2. Coding Help : telegram EA notification

      6 Replies 2840 Views

      by redbulls60, Sun Jan 21, 2018 9:45 pm in Coding Help

      6 Replies
      2840 Views

Return to “Coding Help”

Who is online

Users browsing this forum: CommonCrawl [Bot] and 1 guest