Tüm siparişler
Kurallar
İş tamamlandı
İş Gereklilikleri
The two existing Indicators have been provided (MQ5).
A project was started by a developer to modify these indicators to add audible sound, push notification and selectable time frame features to each of these indicators. The features were added however, some glitches were also created at the same time. I am looking for a developer who can correct these glitches.
Glitches:
QT V5:
How this indicator works: The two lines can converge either at the top of the range (+1) or at the bottom of the range (-1). Some time after they converge, they will then diverge again. This divergence point is the most important decision point of the indicator. An audible notification and push notification are generated at the divergence points.
Glitch 1:
Generating multiple false divergence audible and push notifications. Sometimes, while the current candle is still forming, the lines will briefly diverge and then go back into convergence, which will cause an audible/push notification. I am not interested in momentary divergences that occur before the candle has been completed. I only want to receive an audible/push notification, immediately after the candle has completed/closed (if it closes as a divergence). Please correct this glitch.
Glitch 2:
Selectable timeframe feature not working properly:
Glitch 2A: The QT V5 timeframe selection is not holding when the chart is set to a higher timeframe than the QT V5. For example, if the Chart is set to M1, and the QT V5 is set to M1, it works fine. However, if the Chart is then changed to a higher timeframe (M5, M15, M30, H1, etc), then the QT V5 timeframe appears to change with it. Please correct this glitch.
Glitch 2B: When the QT V5 is set to a higher timeframe than the chart, the lines on the indicator appear very choppy, rather than smooth. Please correct this glitch.
Glitch 3:
Audible alert muting feature does not work when two instances of the QT V5 are being used on the same chart. This indicator includes a button that appears in the bottom left hand corner of the main chart (a green box with a “Q” in it) that is used to mute the audible alarm. This feature works fine when only one instance of the QT V5 is being used however, I sometimes like to use two instances of this indicator, set to different timeframes, on the same chart. When I use two instances, then the mute button does not work. Is there a way of having this mute button feature work and mute both instances of this indicator?
Glitch 4:
Unable to turn off push notifications when two instances of this indicator are running on the same chart at the same time. I typically run this indicator set to M1 and another instance set to M5, at the same time. When I will disable push notifications to both of them, the M1 pushes will stop but the M5 pushes will not stop. Please correct this glitch.
MESA V2:
Glitch 1:
Receiving multiple push notifications. When push notifications are enabled on this indicator, I will receive two notifications each time. One will say “(1 minute)”, which is the timeframe of the chart, and the other one will say “(6 minutes)” which is the timeframe of the indicator. I should only be receiving one push notification at a time, which should be the one that says “(6 minutes)”. Please correct this glitch.
Glitch 2:
Unable to turn off push notifications that say “(6 minutes)”. When I turn off push notifications, I still received the notifications that say “(6 minutes)” (both “crossover” and “early warning” pushes). The only way I’m able to completely stop all push notifications is to simply delete the indicator from the chart. Please correct this glitch so that I do not receive any push notifications when I disable this feature in the properties.
Glitch 3:
The word “Early” is spelled wrong in the Properties window. In the property window, one of the features is called “Alert on Ealy Warning”. Obviously, the word “Early” is spelled wrong. Please correct this spelling error.
Glitch 4:
Receiving false “Early Warning” push notifications (I think).
Here is how this indicator works: The indicator consists of two lines. The fast line is called the MAMA and the slow line is called the FAMA. During an uptrend the MAMA will be above the FAMA and during a downtrend the MAMA will be below the FAMA. A key decision point of this indicator is the crossover point. Some time before the crossover occurs, the MAMA will be angled against the trend. For example, during an uptrend, some time before a crossover occurs, the MAMA will angle downward (against the trend). When this happens, this is an early indication that a crossover may happen soon so, a push notification was created to alert me to this. For some reason, I seem to be receiving multiple false early warning push notifications. Please check into this and confirm that it is happening, and if so, correct the glitch. If the MAMA angles against the trend momentarily while a candle is still forming, I should not receive an early warning push. I should only receive the early warning push after the candle closes and the angle of the MAMA line is finalized.
Glitch 5:
Selectable timeframe feature not working properly. The MESA V2 timeframe selection is not holding when the chart is set to a much higher timeframe than the MESA V2. For example, if the Chart is set to M1, and the QT V5 is set to M6, it works fine. However, if the Chart is then changed to a much higher timeframe (H1, H4, D1 etc), then the MESA V2 timeframe appears to change with it. I also noticed that when the chart is set to a higher timeframe, the push notification will say the timeframe of the chart, rather than the timeframe of the MESA V2 so, I’m thinking these two problems may be related. Please try to correct both of these problems.
A note about future projects:
Note that, once these glitches have been corrected, I will be interested in translating both of these indicators to MQL4 and Pine Script so, if the developer is versed in these languages as well, this will be a plus and will likely look to the same developer to perform this work as well.