[NinjaScriptProperty] attribute

[koganam]

The problem comes when you export that to a compiled assembly (protected dll or not) and try to import it into another system..

That is because of how NT generates the .cs file. It ignores all using statements that are not there by default. You will have to edit the .cs file to put in the using statement.

Here is the long discussion about the matter, a long time ago, when this whole matter of Global Namespace pollution was raised about almost 4 years ago..

ref: http://ninjatrader.com/support/forum...33&postcount=4

I know that you will read the whole thread for context.

Dangnabit, I am giving away too many of my secrets. (rolling eyes at me, not you!)

[ETFVoyageur]

That is because of how NT generates the .cs file. It ignores all using statements that are not there by default. You will have to edit the .cs file to put in the using statement.

Here is the long discussion about the matter, a long time ago, when this whole matter of Global Namespace pollution was raised about almost 4 years ago..

ref: http://ninjatrader.com/support/forum...33&postcount=4

I know that you will read the whole thread for context.

Dangnabit, I am giving away too many of my secrets. (rolling eyes at me, not you!)

It seems to me that there is a bug report / feature request for the Magic Code stuff -- we need a way to inform the Magic Code what "using" statements are needed when its code is in a separate file. The current way is too mysterious for the uninitiated, and pretty annoying for the cognoscenti.

--EV

[koganam]

It seems to me that there is a bug report / feature request for the Magic Code stuff -- we need a way to inform the Magic Code what "using" statements are needed when its code is in a separate file. The current way is too mysterious for the uninitiated, and pretty annoying for the cognoscenti.

--EV

Absolutely agreed. Do not hold your breath: they seem pretty determined that the only way to code is to pollute the Global Namespace.

[ETFVoyageur]

Absolutely agreed. Do not hold your breath: they seem pretty determined that the only way to code is to pollute the Global Namespace.

I hope you are being to negative.

They seem to be trying to provide quality code and a quality development environment. Basically forcing their users into the global namespace is the antithesis of providing a quality environment. Polluting the global namespace is Evil.

Let's hope that whoever from NT reads this will see to it that we get a way to let the Magic Code know what "using" statements it will need for it to compile independently.

--EV

[quicktrick]

Hello!

I have a question about [NinjaScriptProperty].

I have two parameters in my code:

[Range(1, int.MaxValue), NinjaScriptProperty]
[Display(Name = "Parameter1", GroupName = "NinjaScriptParameters", Order = 0)]
public int Parameter1
{ get; set; }

[Range(1, int.MaxValue), NinjaScriptProperty]
[Display(Name = "Parameter2", GroupName = "NinjaScriptParameters", Order = 1)]
public int Parameter2
{ get; set; }

In the UI they are showed in the correct order. "NinjaScript generated code" also uses them in the correct order. But on the chart their data are displayed in the reverse order, like:

MyIndy(ES 12-15(60 Minute), P2, P1)

where P2 and P1 are the values of 'Parameter2' and 'Parameter1'.

Is it a bug or a feature? How can I change the order of displaying the parameters on the chart?

[NinjaTrader_DaveI]

I have a question about [NinjaScriptProperty].

This should not be occurring, and I am not seeing the same thing on my end just by plugging these properties into an existing indicator. Can you please share a script with me which is reliably producing the issue on your end? That may help me to pin the issue down on my end.

[quicktrick]

This should not be occurring, and I am not seeing the same thing on my end just by plugging these properties into an existing indicator. Can you please share a script with me which is reliably producing the issue on your end? That may help me to pin the issue down on my end.

Hello Dave,

I made some tests and found that 'Order' attribute doesn't work for strings displaying on a chart, NT sorts the parameters alphabetically.

I've attached the code.

[NinjaTrader_DaveI]

Thank you. The way that the values are ordered in your script is as expected. As you noted, they are sorted alphabetically, and I was able to confirm that this is the intended behavior. However, it appears that you were seeing something different in your previous example, as I would expect Parameter1 to be listed before Parameter2 alphabetically (as it was for me when I tested using those property names).

Do you find that the properties are not listed alphabetically when the only difference in their names is a number, by chance? For example, if you tried "Test2" and "Test3", would Test3 be listed first on your end?

[quicktrick]

Intended behavior? Really? I'm disappointed. That's illogical. You introduce the 'Order' attribute to make it possible for user to set the desired order in the properties list, but you don't use the same thing in the string displayed on the chart. That's silly. Please, talk it over with NT8's developing team. It's a feature request.

Do you find that the properties are not listed alphabetically when the only difference in their names is a number, by chance? For example, if you tried "Test2" and "Test3", would Test3 be listed first on your end?

No.