limit the use of an indicator from EAs

To add comments, please log in or register
Jean Francois Le Bas
565
Jean Francois Le Bas  

Hi

i'd like to limit the use of an indicator so it cannot be used in EAs

but i'm not sure if it is possible

thanks for help

Jeff

Marcin Madrzak
510
Marcin Madrzak  
Jean Francois Le Bas:

i'd like to limit the use of an indicator so it cannot be used in EAs

but i'm not sure if it is possible

If you are using buffers you can hide them preventing other programs from accessing them via iCustom. You have to use SetIndexLabel(x,NULL); where x is buffer number in OnInit.  https://docs.mql4.com/customind/setindexlabel

If you are using objects there is no good solution bc even hidden objects can be read by another program.

SetIndexLabel - Custom Indicators - MQL4 Reference
SetIndexLabel - Custom Indicators - MQL4 Reference
  • docs.mql4.com
SetIndexLabel - Custom Indicators - MQL4 Reference
Jean Francois Le Bas
565
Jean Francois Le Bas  
Marcin Madrzak:

If you are using buffers you can hide them preventing other programs from accessing them via iCustom. You have to use SetIndexLabel(x,NULL); where x is buffer number in OnInit.  https://docs.mql4.com/customind/setindexlabel

If you are using objects there is no good solution bc even hidden objects can be read by another program.

thank you so much i didn't knew that

Mladen Rakic
132993
Mladen Rakic  
Marcin Madrzak:

If you are using buffers you can hide them preventing other programs from accessing them via iCustom. You have to use SetIndexLabel(x,NULL); where x is buffer number in OnInit.  https://docs.mql4.com/customind/setindexlabel

If you are using objects there is no good solution bc even hidden objects can be read by another program.

That will not prevent accessing the buffer. Buffers (any buffer - displayed or not) can always be accessed using iCustom() regardless if they are displayed in the data window or not
Marcin Madrzak
510
Marcin Madrzak  
Mladen Rakic:
That will not prevent accessing the buffer. Buffers (any buffer - displayed or not) can always be accessed using iCustom() regardless if they are displayed in the data window or not
I was not aware of this. My fault then :) If so then hiding buffers similarly to objects can only make it more difficult to read the data from indicator but not impossible. Seems like there is no solution to completely prevent this. Thanks for correction.
Pavel Shutovskiy
72706
Pavel Shutovskiy  
iCustom accepts a limited list of input parameters of the indicator no more than 59 parameters, under the main settings, make a description and on the 60-61 line of settings, create the parameter enabling the indicator
Jean Francois Le Bas
565
Jean Francois Le Bas  
Pavel Shutovskiy:
iCustom accepts a limited list of input parameters of the indicator no more than 59 parameters, under the main settings, make a description and on the 60-61 line of settings, create the parameter enabling the indicator

thanks i'll try that

To add comments, please log in or register