• Join us

Requests & Ideas - page 175

Mladen Rakic
163289
Mladen Rakic  

winner246

Leosony2 indicator is a decompiled indicator

winner246:
HELLO MLADEN, I WOULD GREATLY APPRECIATE IF YOU COULD KINDLY CREATE THIS INDICATOR. I HAVE ATTACHED 3 INDICATORS THAT ARE RELEVANT FOR THIS DESIGN. ( 1 ) THE INDICATOR IS SIMPLY HIGHLIGHTING SPECIFIC TOP AND BOTTOM PRICES AS INDICATED BY THE FIRST DOT OF THE PARABOLIC SAR EITHER FOR BUY OR FOR SELL. ( 2 ) THE INDICATOR WILL NEVER SHOW THE 2nd AND SUBSEQUENT BARS (PRICE) OF THE SAR. IT WILL ALWAYS SHOW JUST THE PRICE OF THE FIRST DOT OF THE SAR BUY SIGNAL OR THE FIRST DOT OF THE SAR SELL SIGNAL . ( 3 ) ONCE THE SAR REVERSES (e.g ABOVE THE PRICE BAR ) THE PRICE OF THIS FIRST DOT OF SAR BECOMES THE BOUNDARY LINE( HORIZONTAL AS IN LEOSONY2 ) THAT WILL CONTINUE EXTENDING HORIZONTALLY AT THE CLOSE OF EVERY NEW BAR UNTIL THE SAR REVERSES TO THE OPPOSITE DIRECTION . ( 4 ) ONCE THE SAR REVERSES, THE HORIZONTAL DOTS WILL STOP ON THE PREVIOUS SIDE AND START SHOWING ON THE OPPOSITE SIDE THE SAR HAS JUST REVERSED TO ( FOLLOWING THE PRICE OF THE FIRST DOT OF SAR.) ( 5 ) PLEASE PLACE A SMALL BOX OF THE SPECIFIC PRICE LEVEL BY THE LEFT OF THE HORIZONTAL LINE (JUST AS IN BROOKY ) ( 6 ) FINALLY PLEASE USE THE FORMULA OF YOUR PARABOLIC SAR 2 WITH ITS OPTION TO USE CLOSE/CLOSE INSTEAD OF HIGH/LOW . THANKS FOR THE GREAT WORK.
winner246
330
winner246  

Sar support and resistance

Hello mladen, just noticed you are on site, please do i expect something for post 1739 ? Thanks for the great service you are rendering, its simply invaluable.

Mladen Rakic
163289
Mladen Rakic  

winner246

I am on site quite frequently, but the problem with that post is different.

Please read my previous post about leosony2 indicator (I have told more than once that I am not altering nor using decompiled indicators, and since that one is a decompiled indicator, it must be excluded from anything related to coding here. Sorry but I am not going to change my point of view regarding decompiled code)

winner246:
Hello mladen, just noticed you are on site, please do i expect something for post 1739 ? Thanks for the great service you are rendering, its simply invaluable.
winner246
330
winner246  

Sar support and resistance

Hello mladen, there is nothing required from leosony2 , i made reference to it just for the design of horizontal dots, i believe you must done similar design with some other indicators, good to hear from you. PB. PLEASE IGNORE THAT INDICATOR ( LEOSONY2 ) YOUR POINT IS NOTED.

halvardu
131
halvardu  

Hi Mladen..

Could you please make 2 alarms on this indicator?

Alarm1: Is when it touches either the bottom line or the top line.

Alarm2: Is when it breakes and closes below/over the bottom or top line.

It should also be possible to turn the alarms on/off.

Thanks in advance!

Halvard

equdistant_channel_-_semi-automatic.mq4

halvardu:

Forgot the indicator..

Mladen Rakic
163289
Mladen Rakic  

...

Halvard

"Touching" is a highly subjective category as far as computer programs are concerned. we (men) consider touches when something is even just visually close to something else and we consider those values as "touching". As far as computer is concerned touch would be only in case when two values are completely the same which is a very, very rare case. So in order to have "touches" on two values some tolerance must be introduced (for example if abs( value1 - value2) < 1 pip) or rounding must be done, but then that directly overlaps with crosses conditions. That is one of the reasons I do not like to code "touches" : what looks like a touch to you will almost sure not look like a touch to a PC and it is so highly dependent on our perception and different time frames (2 pip distance on a monthly chart will for sure look the same as 1 pip distance to our eye on a monthly chart, while to PC it will not be so). The second reason why I don't like touches is that if they are applied to current bar, there are going to be "touches" whenever price crosses the other value (at some stage they will fall into the tolerance range) and then it will become a cross.

In my mind touches on PC are falling into same category as divergence : men can see it very easy while PC can not

As far as crosses are concerned, they are uniquely definable so a code can not make mistake as far as that is concerned and it can be done

___________________________________

Hope you don't mind this a bit lengthier post, but I thought that I should tell these things

halvardu:
Hi Mladen..

Could you please make 2 alarms on this indicator?

Alarm1: Is when it touches either the bottom line or the top line.

Alarm2: Is when it breakes and closes below/over the bottom or top line.

It should also be possible to turn the alarms on/off.

Thanks in advance!

Halvard

equdistant_channel_-_semi-automatic.mq4
halvardu
131
halvardu  

Thanks for the reply Mladen

Maybe it can alert when the price move true the line and then retrace again, it will then not be a break but a proberly retracement in price?. If this is not possible? can you please make the break alert, when the close price break the channel?.

Here is a picture of what i had in mind..

Thanks alot

Halvard

mladen:
Halvard

"Touching" is a highly subjective category as far as computer programs are concerned. we (men) consider touches when something is even just visually close to something else and we consider those values as "touching". As far as computer is concerned touch would be only in case when two values are completely the same which is a very, very rare case. So in order to have "touches" on two values some tolerance must be introduced (for example if abs( value1 - value2) < 1 pip) or rounding must be done, but then that directly overlaps with crosses conditions. That is one of the reasons I do not like to code "touches" : what looks like a touch to you will almost sure not look like a touch to a PC and it is so highly dependent on our perception and different time frames (2 pip distance on a monthly chart will for sure look the same as 1 pip distance to our eye on a monthly chart, while to PC it will not be so). The second reason why I don't like touches is that if they are applied to current bar, there are going to be "touches" whenever price crosses the other value (at some stage they will fall into the tolerance range) and then it will become a cross.

In my mind touches on PC are falling into same category as divergence : men can see it very easy while PC can not

As far as crosses are concerned, they are uniquely definable so a code can not make mistake as far as that is concerned and it can be done

___________________________________

Hope you don't mind this a bit lengthier post, but I thought that I should tell these things
Files:
channel.gif 298 kb
Mladen Rakic
163289
Mladen Rakic  

OK

Will be done

halvardu:
Thanks for the reply Mladen

Maybe it can alert when the price move true the line and then retrace again, it will then not be a break but a proberly retracement in price?. If this is not possible? can you please make the break alert, when the close price break the channel?.

Thanks alot

Halvard
Mladen Rakic
163289
Mladen Rakic  

...

Halvard,

It seems that the ObjectGetValueByShift() that is usually used to get values (price) of an object at a specific bar, does not work with channel type objects (that indicator is actually an object drawn on chart). Without that it is not possible to know the exact price values of channel lines at specified bars. Will try to find some solution for that, but so far I did not find any.

Just wanted to keep you updated as far as that indicator is concerned

halvardu
131
halvardu  

Hi, thanks for the update Mladen . Maybe its better to use another type of channel indicator for this?? but I think you know that better than me .

Thanks for the help

Regards

Halvard

mladen:
Halvard,

It seems that the ObjectGetValueByShift() that is usually used to get values (price) of an object at a specific bar, does not work with channel type objects (that indicator is actually an object drawn on chart). Without that it is not possible to know the exact price values of channel lines at specified bars. Will try to find some solution for that, but so far I did not find any.

Just wanted to keep you updated as far as that indicator is concerned