Doublema

[WhoKnows]

Couple of questions:
- Is there a reason why PriceTypeSupported is set to "false"? (In DoubleMA.cs line 59 and MAV.cs line 65). Enabling it to true gives some extra options to 'shift' the averages as you can use Open and Close as input ... but you may have had a specific reason to put it on false.

- I first thought the selection of MA was handled in MAType.cs, but apparently it is in the MAV.cs. Is that MAType.cs still needed?

- Looking at MAV.cs I get confused (looking at the parts commented out I think this has been some work in progress).
I am no programmer ) but trying to learn via analyzing the code of others. As I read it this file first started with a public enum MAType (line29-59). I thought the numbers after the MAType refered to the cases in 78-92 via the command 'switch'... however the numbers do not correspond to the ordering of the cases. And the section with cases is also commented out.

In line 105-147 under OnBarUpdate a new range of options is given via if .. else if ..statements.And that list is replicated under properties (194-261).

As I wanted to add TEMA I added this in both lists. Is it important that the order in these lists is the same?
After the compiler complained I also added 'TEMA=16' under public enum.
Apparently it works, but what does this =16 do when it does not refer to anything in a list?

Anyway, thanks to the programmers ... it sure helps to get smoothing.

[ctrlbrk]

Couple of questions:
- Is there a reason why PriceTypeSupported is set to "false"? (In DoubleMA.cs line 59 and MAV.cs line 65). Enabling it to true gives some extra options to 'shift' the averages as you can use Open and Close as input ... but you may have had a specific reason to put it on false.

No reason I can think of, should be supported but have not tested.

- I first thought the selection of MA was handled in MAType.cs, but apparently it is in the MAV.cs. Is that MAType.cs still needed?

No that was a mistake on my end. Keeping track of all these individual add-ons to indicators for enum lists and etc is a pain, especially when their naming convention has nothing in common with the base indicator. I will strive to clean that up if I do another release of DoubleMA. Remember, I am not original author.

- Looking at MAV.cs I get confused (looking at the parts commented out I think this has been some work in progress).

Just nuke the commented out stuff. There are three places you need to modify the code if you want to add indicators, and you need to maintain the order. #varliables, you need to modify the enum integer list. #onbarupdate, and #parms.

I am no programmer ) but trying to learn via analyzing the code of others. As I read it this file first started with a public enum MAType (line29-59). I thought the numbers after the MAType refered to the cases in 78-92 via the command 'switch'... however the numbers do not correspond to the ordering of the cases. And the section with cases is also commented out.

They should correspond. I just looked at mine, they match up. Are you sure, maybe I missed something when I was editing. If they don't match correctly then when you select "ZeroLagEMA" from the list you may be getting a "HMA" or who knows what.

As I wanted to add TEMA I added this in both lists. Is it important that the order in these lists is the same?

After the compiler complained I also added 'TEMA=16' under public enum.
Apparently it works, but what does this =16 do when it does not refer to anything in a list?

The 16 needs to match the enum and case list for TEMA or whatever. Also keep in mind some indicators "output" result is very different, so you have to keep this in mind. You can still use DoubleMA to just color any MA, just select the one MA and set the second one to None. But when you combine to MA's you need to keep in mind their differences.

Mike