FXCodeBase.COM: Forex Chart Indicators and Development

Hiya Nikolay,
Can I use or pass the 'value' from an indicator into another indicator?

For example, using the new 'pivot.lua' indicator that is in Beta (seeing as can use this on other timeframes), how can I just use the PP (pivot point) value in another indicator rather than having to try to combine the two indicators so that I can use it to calculate/use on other calculations in a new indicator? ie;

if PP(from beta) is >= XXXX (in new indicator) then
YYYY = 2 (in new indicator)

Obviously both indicators would need to be run together on charts and I assume that if PP value changes due to scolling back or forward that PP would be updated accordingly!

Can you post a simple example of what I need to include in a new indicator to do this and where.

Also can you maybe give an estimate on how many hours it would take to write and test same pivot.lua that is in Beta, so I can get a better idea of $$cost of such an indicator?

Cheers
LordTwig

Yes, surely.

In the Marketscope, when a new indicator is created, there are three "tuning" tabs: parameters, source and location.

Using the source tab you can select any of the existing sources (prices and indicators) on the chart. Looks at the snapshot in the viewtopic.php?f=27&t=486#p855, this is how I created it. And this is how the source selector looks:

and this is BB applied on PIVOT. Heh... looks so funny.


You can also use other indicators in another indicator code. Use core.indicators table to list and create the indicators. An example of such indicator is also in the Rubicon CCI topic I pointed above.

LordTwig wrote:Also can you maybe give an estimate on how many hours it would take to write and test same pivot.lua that is in Beta, so I can get a better idea of $$cost of such an indicator?

I would still like an estimate $$ on this, if you could, as I may still ask to have my indicator built,
I am pretty close with it at moment but it is buggy and some calculating errors.

I probably still need another couple of months of programming experience yet.

So estimation on this which is similar type would be good

Regards
LordTwig

It depends on the experience. I spent one day to write and debug the existing pivot indicator for the standard levels and then 2 hours to add camarilla/woodie levels and another 1 hour to provide the "historical" mode finally. So, 1,5 of work-day.

The indicators which does not require additional data loading it's usually much faster. For example DEROSC oscillator I published the list time was made in 15 minutes.

Nikolay.Gekht wrote:It depends on the experience. I spent one day to write and debug the existing pivot indicator for the standard levels and then 2 hours to add camarilla/woodie levels and another 1 hour to provide the "historical" mode finally. So, 1,5 of work-day.

I think it is great! Much better than previously, great that you added Carmarilla & Woodie, and I like the historical or today option, well done.
LordTwig