#region C# command - NinjaScript

[nientenickgraze]

Hello, I know you had already received this issue but the C# command " #region " ALWAYS messes up both for brand new indicators/strategues and old ones...

Please, could you be so kind to give us any progress you're making about this, if any ?
I am sorry but is really annoying and frustrating coding and, just few seconds after, losing your "structure" inside you script.
I am sorry contacting you while you are fixing bigger issues, but no way to concentrate and finish the script in time.

Please, give any feedback if you can.

Thank you very much
Cavallo Pazzo

PS: here attached the issue that occurs both on indicators and strategies scripts...

[NinjaTrader_Matthew]

All of the scenarios we were aware this misbehavior could occur has been confirmed to be fixed in the next beta release - NTEIGHT-8689

[nientenickgraze]

ok...

Thank you for this update Matthew.

Cavallo Pazzo

[nientenickgraze]

Hello Matthew,

inside the Beta4 the "#region ...some code ... #endregion" has not been fixed.
I have the same issue now.

Thanks,
Andrea

[NinjaTrader_Matthew]

Hello Matthew,

inside the Beta4 the "#region ...some code ... #endregion" has not been fixed.
I have the same issue now.

Thanks,
Andrea

It has been working for me with no issues, but there could be some corner cases we're not aware of. Can you please give exact steps to reproduce or a video so we can review?

[nientenickgraze]

Video Requested

Hello Matthew,

sorry for the delay.
Please, find here attached the video requested.

Let me know how can I help any further...

CP

[-=Edge=-]

It has been working for me with no issues, but there could be some corner cases we're not aware of. Can you please give exact steps to reproduce or a video so we can review?

The ninjascript generated code has always and still uncollapse anytime you compile.

It's definitely much better than before, but there are still times when adding/editing various code that every region will also uncollapse..

I haven't been able to nail down exactly when and what causes this, as I'm still unable to duplicate the experience in small sample code.. Seems to only happen when I'm working in code that has hundreds and/or thousands of lines with many nested regions.. (go figure )

I have noticed that at times when I have commented code // in spots and then comment out the whole region and/or several lines both above and below creating double and/or triple comments //// ////// in spots.. that the regions stop working all together.. But again I've been unable to duplicate this in any type of sample code..

If and when I can provide exact samples I will.. but just thought I'd share my experience as well.. It's definitely much better, but still a couple quarks..

Thanks for all the hard work!

[DaFish]

I am also having this issue, using Beta 6. Beta 5 had it too.

No compile errors... as EDGE says, it maybe related to // or /// throughout the regions - but this would be a guess on our parts.

Really annoying when you have lots of code.

[strategesis]

Yes, this still occurs in B6. I have noticed that one way to trigger it is to add a new line of text.

[nientenickgraze]

I gave up, unfortunately.
Still coding with this issue !

But I know in B7 it will be fixed.

Let us report as many bugs/issue we can find to help Support guys to realize what they need.

Enjoy your sunday
CP