Announcement

Collapse
No announcement yet.

Partner 728x90

Collapse

Why duplicate declarations in built-in indicator?

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

    Why duplicate declarations in built-in indicator?

    in CurrentDayOHLC indicator's (built-in indicator) source we see, that the six fields (currentDate, currentOpen , etc...) are assigned value in class declaration:

    private DateTime currentDate = Core.Globals.MinDate;
    ...


    and also, in state.configure.

    currentDate = Core.Globals.MinDate;
    ...



    I'm interested, generally, why the value assignment is needed two times? isn't it enough, when in class declaration they have values assigned already?

    #2
    Hello TazoTodua,
    Thanks for your post.

    Generally you are correct that you would not need to assign a value twice like it is done in this indicator.

    Looks like the development team simply wanted to ensure that it was assigned once during OnStateChange. This would ensure that value is updated when the indicator is added to the list of applied objects.
    Josh G.NinjaTrader Customer Service

    Comment

    Latest Posts

    Collapse

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