NinjaScript editor #region un-collapsing.

[seahn]

Is there a way to stop the Ninjascript editor un-collapsing my code #region(s) and functions every time the script is compiled. This is very annoying and a time waster. It also defeats the purpose of #region i.e. hiding code not being worked on to make getting around the code easier.

[NinjaTrader_ChrisSch]

Hello seahn,

Thank you for your note.

What version of NinjaTrader are you currently running?

The regions would be expected to collapse upon compiling your code. I have tested this and my regions are collapsing upon compile. However, the body of your code is expected to expand after compiling. Are you finding that your regions specifically are expanding and not collapsing or do you mean something else?

If it is just the regions that are expanding then we would want to take a look at the code itself and attempt to reproduce. If you could attach the .cs file to an email to platformsupport[AT]ninjatrader[DOT]com with "ATTN CHRIS S" in the subject line, I will be happy to look into this further.

Thank you and I look forward to your reply.

[seahn]

I am using NT8.

The regions and functions in my code which I manually collapse seem to randomly expand after compilation I cannot seem to reproduce it consistently, sometimes just one or two regions get expanded other times every function in the script gets expanded. As you can imagine it is very frustrating in a large script to have all the code I have just spent minutes collapsing because I am not working on it be expanded again when I recompile.

But the point is the collapsed/expanded state of any text should not be affected by compilation that is how all editors I have used behave such as Visual Studio.

[NinjaTrader_AlanP]

Hello seahn,

Under Control Center>Help>About, next to version, what is the number you see? For example, 8.0.2.0.

I look forward to your reply.

[seahn]

Nt 8.0.4.0

[NinjaTrader_AlanP]

Hello,

Thank you for your note.

Without the full code we're unable to test on our end.

If you'd like to upload the full code I can take a look and see if anything jumps out. Or if you'd prefer to email a copy, send to platformsupport[at]ninjatrader[dot]com with Attn: Alan P in the Subject line. Also within the email please include a link to this thread, and the files.

I look forward to your reply.

[-=Edge=-]

Without the full code we're unable to test on our end.

This has been an ongoing problem since early in the beta cycle..

http://ninjatrader.com/support/forum/showthread.php?t=77358&highlight=region

Was a lot worse early on.. but the problem being described here, is the same as my comment from late 2015 in the above thread.. This has been a long standing problem with working in NT8's editor, and remains to be a major pain..

[seahn]

This has been an ongoing problem since early in the beta cycle..

This has been a problem going back to NT7.

At this point I kind of feel like I am just getting the run around on the issue, it happens regularly for me with all types of scripts yet they "cannot reproduce the problem". I doubt NT will do anything about this since the editor is 3rd party software I believe.

I am working around the issue by using the Visual Studio link in the NT8 script editor. I can do all my editing in VS then save the file (Ctrl-S). The NT8 editor sees the code has changed and automatically compiles the script. Its pretty seamless, I just minimize the NT8 editor and forget about it.

Anyone that wants to edit with Visual Studio if you do not have it Microsoft has Visual Studio Community Edition which is free just Google it. Just be sure you do not compile in VS and do not save the solution when done.

[sledge]

Oh, the run around, around here. YUPPPPP

The highlighting with /* and */ is also still a problem. Using 3rd party softwares has it plus and minus. Is the 3rd party to blame?

[marty087]

Yes... This is all happening.

[NinjaTrader_AlanP]

Hello marty087 and seahn,

Development is aware of the issue and working on a resolution.

Thank you for your patience.

[JerryWar]

I was able to get rid of most instances of this issue by going thru my code
and making sure that I did not have double // // comment slashes on any one line.
However in some regions I was unable to fix the region collapse based on this theory albeit
it did fix most.

[-=Edge=-]

Without the full code we're unable to test on our end.

Not sure if this will help.. but duplicating these issues is not difficult.. Throw this in your indicator folder and open in editor..

1st thing to notice is that regions don't work at all unless they encompasses the entire method. Notice because the OnStateChange region is inside the override method but the endregion is not.. It doesn't even recognize it as a region..

Now left click on line 122 or 123 in the editor and delete it..
or tab the endregion line 55 over 1...
or I could come up with other scenarios of inserting lines of code.. that will....

Immediately expand all regions...

[NinjaTrader_AlanP]

Hello =Edge=-,

Thank you for the information and steps to reproduce; I have passed this on to development.

Please let us know if you need further assistance.