thread: Recent Strength indicator

I've started a new thread to come up with automation chances - https://www.cliqforex.com/trading-sy...usd-1-pip.html.

The ribbon has my usual posting restrictions; there's information about obtaining these lifted in the bottom of place 1. Kibed, yours are lifted.

I have started a new thread to come up with automation chances - https://www.cliqforex.com/trading-sy...orrection.html.

The ribbon has my usual posting limitations; there is information about getting these lifted in the bottom of place 1. Kibed, yours are lifted.

Steve,

Outstanding, I will follow improvements in your new thread.

David

Hi David,

....

Identifier. This indy is a fashion identifier that is real-time. This confirms the direction of a fashion and help filter out bad transactions. Normally I would think about a transaction when arrows Both D1 H4 agrees and shows one direction, or whenever arrows H4,H1,M30,M15,M5 all agree and shows one direction....

Joyful Piping
Benji

Hello,

Can you happen to get this indi in .mq4 format?

Thanks!

Hello,

Can you happen to get this indi in .mq4 format?

Thanks!

Yes, I have yet another version smiler to what you are asking, for some motives am not able to upload it here as an attachment. You may want to PM your email I need to be able to send it being provided by me.

FYI what you are asking is an indy I was using long time past when Resent power indy first came to my attention,since then I have begun to perform additional RD to improve the egy to what is described here on egy description and tools attachment.

Benji.

Hi Benji,

Anyway, if I can not replicate the problem, I'll think about the possibility of rewriting the indy as soon as I get some spare time. The first attempt was a demo geared toward showing what was possible. I reproduced the concept (and a number of the code) from a TDI alerts indy that I had previously written. Perhaps it would be simpler to code the evaluations to the genuine indy itself, as opposed to have them parameters -- especially if you would like the indy to alert immediately two currencies fulfill conflicting conditions concurrently (a single gt; 50; just one lt; 50).

David...

Hi David,

I trust this finds you when your head is clear. Let me know when you've discovered a way.

As you'd earlier explained,you have very limited time available here in FF due to other overpowering commnts you are currently undertaking.Am aware I choose to hold my patience.

Benji

Hi David,

I trust this finds you when your head is clear. Allow me to know if you have found a way.

As you'd previously explained,you have very limited time available here at FF because of additional overpowering commnts you are currently undertaking.Am conscious I opt to hold my patience.

Benji

Hi Benji,

I apologize. I feel terrible about not having gotten back to you earlier.

I will try to finish your alarms indy during the next few days. Can you affirm the Word document that you connected to article #274 is still a specifiion? Or should I be looking at a number of the posts in your Trading profitably using RS thread?

Thanks,
David

Hi Benji,

I apologize. I feel awful about not having gotten back to you earlier.

I will try to complete your alerts indy over the upcoming few days. Can you affirm that the Word document that you attached to post #274 remains a specifiion? Or should I be looking at some of the posts in your Trading profitably using RS thread?

Thanks,
David

Hi David,

Very well, I have tried to explain these alerts conditions on two different posts i.e #274 Post #281. I'd prefer you concentrate on tools attachment and egy description on post #281 that has detailed information under conditions.

With these alerts am seeking to achieve the next;User will get an choice to select preferred pairs that he wishes to concentrate be alerted on. User will get an choice. User will get an choice to enter time interval between receiving alerts, also favored session or time period. User will get an choice to choose how to be alerted independently by sound or by email. A display of the information on a window that is different or on precisely the same window using RS would be even better. Above info on bullets are only guidelines, you may wish to upgrade on them or ignore them, that is within your discretion as a developer .

Benji

Hi David,

Very well, I have tried to describe these alarms requirements on 2 different articles i.e #274 Post #281. I'd like you focus on tools attachment and egy description on article #281 that has detailed information under alert conditions.

With such alarms am trying to achieve the next;
[list][*] User will have an option to select preferred pairs he wishes to focus be alerted on.[*] User will have an option.[*] User will have an...

OK, this is a lot more complicated than what I previously believed. This evening I will have a look.

Sorry, I missed your notes in post #281 when I looked yesterday.

Please note, I can test only Recent Strength, not circumstances involving FXI_PivotPoints, Daily Range, etc when generating alarms.

By favored pairs, I suppose that you mean currencies. Recent deals with currencies, not pairs. Alerts can be generated only for currencies.

The sound alert will also be observable, hence I presume a visible display of those above.... Doesn't require separate coding. It will be observable in whatever chart you attach the new indy to. This really is a MT4 restriction, I can not do anything about it.

David

OK, this is a lot more complex than what I thought. This evening, I will have a look.

Sorry, I missed your notes in post #281 once I looked yesterday.

Please note, I will test just Recent Strength, not circumstances involving FXI_PivotPoints, Daily Range, etc when generating alerts.

By preferred pairs, I suppose that you mean currencies. Recent deals with currencies, not pairs. Alerts can be generated just for currencies.

The sound alert are also visible, hence I presume a visible display of the aforementioned.... Does not require...

Yes, please concentrate on generating alarms testing Resent Strength alerts.

Yes By preferred pairs, I mean currencies.

In relation to sound on alerts I concur, sound cannot be more visible than its own is on MT4,I guess I made a gross mistake right there!!

I will be delighted to clarify any information you might need.

Benji.

Yes, please focus on creating alerts testing Resent Strength alerts.

Yes With preferred pairs, I mean currencies.

In regards to sound on alarms I concur, sound may not be more visible than its is on MT4,I guess I made a gross mistake right there!!

I will be happy to clarify any information you might require.

Benji.

Hi Benji,

I have attached the indy RSalerts.mq4 to place #1; put in in the.../experts/indiors folder and then restart MT4.

The Present Strength.ex4 indy must already be running with the OutputFile set to Presets--Recent Strength.csv
This will construct the file that is required by RSalerts.mq4
Considering that the Recent Strength parameters dominate the values that get output to this document, they will also affect the manner in which the alarms get generated.

Attach RSalerts.mq4 to Another chart to Recent Strength. The pair doesn't matter, but the interval will determine how often the alarms get assessed. By way of instance, if you would like the alarms to be assessed each hour, attach the RSalerts.mq4 indy to a H1 chart.


PARAMETERS

FileName #8212; must be abandoned as the default value, i.e. must be the same file that has been assembled from the Recent Strength indy.

AlertCurrencies #8212; alarms will just get generated for the currencies in this list. You must separate your entries with commas.

AlertTimeframes #8212; specify valid timeframes, separated by commas.
-- A strong currency is one that has 1st, 2nd or 3rd highest rank at datapoint #0 (the rightmost datapoint) in EVERY interval that you specify.
-- A weak currency is one that has 1st, 2nd or 3rd lowest rank at datapoint #0 (the rightmost datapoint) in EVERY interval that you specify.
-- A currency that is neither strong nor weak is neutral
-- To get an alert to be generated, there must be at least one strong and at least one weak currency. Also, the currency must have altered its rating (strong, neutral or weak) since the alarms were last checked, in order to get the alert to be generated that currency. (This will ensure that alarms are not generated repeatedly while evaluations remain unchanged)

AlertsBetween #8212; this controls between which times alarms are permitted to occur. The format must be hh:mm:ss,hh:mm:ss in which the first entry (before the comma) is the from time along with the second entry (after the comma) is the double time time.
-- When the from time is sooner than the thru time, then alarms will be generated only when the br0ker's MT4 time is between the from time along with the thru time. E.g. if your entry is 04:00:00,06:00:00 then alarms will be generated only between 4am and 6am (MT4 time).
-- When the time is later than the thru time, then alarms will be generated only when the br0ker's MT4 period is between time along with the thru time, across a midnight barrier. E.g. if your entry is 23:00:00,01:00:00 then alarms will be generated only between 11pm and 1am the following day (MT4 time).

The next two parameters control which type of alert will be generated:

ChartAlerts #8212; if TRUE, this may sound/display the familiar MT4 audio/visual alert to the chart (to which RSalerts.mq4 is connected ).

EmailSubject #8212; leave clean = no email alerts will be sent. Whatever text you type will appear as the email subject, if non-blank.


The attentive text looks something like this:
RS alarms [AUDUSD,M15] powerful =EUR,JPY, feeble =AUD,NZD,
The values within the square brackets are the pair/timeframe of this chart to which the RSalerts.mq4 indy is connected (as already explained, the interval also determines how often alerts are checked).
From the aforementioned example, suitable pairs to trade (based on which are provided by your br0ker): buy EURAUD, EURNZD; market AUDJPY, NZDJPY


I have done some preliminary testing. Please examine it more comprehensively and let me know what you think.

When it turned out, this was an easier programming project than I originally envisaged.
But that's partially because I have digressed from the open-endedness principle I've previously attempted to remain with. This is an indior. And it's my past freebee offering at FF; I must pay my bills.

David