I was looking at the FD coding & suddenly realized that there were alot of unncessary display buffers used up already (eg. 2 additional parallel display lines centred around the main FD display line etc). Not sure if the 7/8 buffers being used up is the issue that is causing you a headache, but you can delete the unnecessary buffers. A friend (who has minimal coding knowledge, same as me) was telling me to suggest to you the possibility of making an indicator of an indicator, if that might help in reducing your coding difficulties. I am fine with any general format/type of implementation.
Hope this would help in reducing the coding difficulties on your side. Sorry for causing you a headache & once again thanks for everything
I think that it will need to be rewritten (in order to make it clean for any upgrades and in order to make it efficient). Also found a couple of points in the code that will make it a repainting indicator (not too obvious at the first glance, but they do exist in the code)
Mladen, revisiting the alerts you made, are you able to create 2 different sound alerts, sound A when it is up/down the conditions, and sound B when it is neutral? Thanks.
Here is a version in which you can specify a different sound for each of the 3 alert types
Mladen, thanks for the speedy work. I have no prior experience with changing of sound files, I tried specifiying stops.wav for the neutral sound but somehow I still heart alerts2 being sounded. Am I doing something wrong?
Turn the sounds in the options->events off and then only the sound from the indicator will be heard (like this :
Thanks for the tip, Mladen.
Mladen, I just realized there isn't an "AlertOnCurrent" parameter. I would like an AlertOnCurrent parameter with the option of specifiying the choice of AlertOnCurrent for Up/Down all conditions, and AlertOnCurrent for Neutral conditions. Thanks Mladen!
we have discussed that issue at the time when we were talking about the creation of the indicator : it always has to be on current (since it is managing 4 different time frames at some occasions) It can not be different when 4 different time frames are processed
Mladen, I understand. I was thinking that the alerts would sound when all are above conditions / below conditions / neutral based on the status of the previous closed candle, with options (a) AlertsOnCurrent (false) for Above/Below conditions and (b) AlertsOnCurrent (false) for Neutral (just in case I want to be alerted immediately on current candle for trade exits). Wouldn't this be possible?
Here is an example :
The indicator would be set to use 1hour, daily, weekly and monthly time frames. If we would look for closed bars alerts then we would have to combine signals from 1 hour ago, 1 day ago, 1 week ago and 1 month ago. As you can see they simply are not pointing to same time at all and combining signals from times so different is dangerous and, in my opinion, without any sense