Bug followup -- Description and enum

[ETFVoyageur]

Remember the bugs I discovered -- that the class Description string cannot take a string expression (I do not know about parameters), and that an enum that is the type of a parameter must pollute the global namespace?

It turns out I was not the only one with the problem. I am reading through the contributed V7 version of HeikenAshi_Smoothed, and it has both problems. As with me, the author (probably) never noticed because of the related bug that the build does not error out on a description string expression -- it just silently fails to generate updated Magic Code at the bottom. I have sent him email detailing the problems.

I wonder how much other code is silently building wrong?

--EV

[NinjaTrader_Brett]

Hello,

Checking with development on this.

[NinjaTrader_Brett]

Hello,

There are no updates on this from development.

Let me know if I can be of further assistance.

[ETFVoyageur]

No problem. I understand those bugs, and have long since moved on.

I have previously reported those three bugs, and was just pointing out that some of the indicators you have available for people have these same bugs.

(a) It is not just I who tries to do those things, which I consider very reasonable.

(b) The contributed indicators that have those same bugs are not good examples for others to copy.

(c) The fact that those bugs exist supports my point that it is a serious bug that the build gives no warning that it could not build correctly in these cases (i.e. it could not generate the Magic Code at the end).

Do what you wish with the information.

--EV

[NinjaTrader_Brett]

Hello,

WIll forward to development.

Thanks for further update. It is currently unsupported to use + signs in the dewcription XML field. However I will send the infromation in for their consideration.

Thank You.

[ETFVoyageur]

The one thing I think is the most important is that the build recognize when it fails. When it cannot generate the Magic Code, there must be an error for the user.

--EV