Announcement

Collapse
No announcement yet.

Partner 728x90

Collapse

NT7 Lock up on programming mistake...

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    NT7 Lock up on programming mistake...

    Guys, 7.0.0.13 locked up on me as I was loading an indicator I was writing. After various file deletions, a reinstallion (repair), and numerous unsuccessful attempts to restart afterwards, I am finally able to successfully open NT7 again.

    The problem was an unintentional error in the font code I was writing. I made the mistake of equating the font's public parameter with its previously defined private variable, as follows:

    [XmlIgnore()] [Description("Font for text.")] [Category("My Parameters")]
    public Font TextFont {get {return textFont;} set {TextFont=value;}}
    [Browsable(false)] publicstring TextFontSerialize
    {get {return NinjaTrader.Gui.Design.SerializableFont.ToString(T extFont);}
    set {TextFont=NinjaTrader.Gui.Design.SerializableFont. FromString(value);}}

    To be correct, all but the first version of "TextFont" should be "textFont" to differentiate the parameter from the variable. That mistake was enough to lock up NT and make it impossible to re-open. Ultimately, the solution was to delete my default workspace and rename a second workspace with my default workspace's name, then restart NT. That prevented NT from loading a chart with the incorrect code, as it was trying to do on startup and failing.

    Obviously the error could have been more easily prevented if I had used less-similar file names. Still, it would be helpful if NT's compiler put up an exception for this type of programming mistake.

    Otherwise, NT7 is working great. I hope this helps,

    Light

    #2
    Those inifite loops errors surely can get you in trouble. Thanks for bringing this to our attention.
    RayNinjaTrader Customer Service

    Comment


      #3
      Another solution...

      Thanks Ray. One other note about this... The problem was significantly compounded by the fact that NT7 automatically saved the error-causing workspace and tried to reopen it on every attempted restart. When NT7 locked up, I had to shut it down from the Task Manager, and being unable to show the message box "Do you want to save workspace ...?", NT7 apparently took the default answer as "yes". That not only over-wrote my workspace with an error-causing replacement, but it meant I couldn't reopen NT, since every restart tried to reopen the automatically-saved faulty workspace.

      This might be solved if the default answer to the save-workspace message box were "No". It's not a big issue, but I thought I should mention it.

      NT7 is excellent. Thanks for the great work!

      Light

      Comment


        #4
        Light, we appreciate the kind feedback and suggestion - thanks.

        Comment

        Latest Posts

        Collapse

        Topics Statistics Last Post
        Started by Geovanny Suaza, 02-11-2026, 06:32 PM
        0 responses
        600 views
        0 likes
        Last Post Geovanny Suaza  
        Started by Geovanny Suaza, 02-11-2026, 05:51 PM
        0 responses
        347 views
        1 like
        Last Post Geovanny Suaza  
        Started by Mindset, 02-09-2026, 11:44 AM
        0 responses
        103 views
        0 likes
        Last Post Mindset
        by Mindset
         
        Started by Geovanny Suaza, 02-02-2026, 12:30 PM
        0 responses
        558 views
        1 like
        Last Post Geovanny Suaza  
        Started by RFrosty, 01-28-2026, 06:49 PM
        0 responses
        558 views
        1 like
        Last Post RFrosty
        by RFrosty
         
        Working...
        X