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 Hwop38, 05-04-2026, 07:02 PM
    0 responses
    152 views
    0 likes
    Last Post Hwop38
    by Hwop38
     
    Started by CaptainJack, 04-24-2026, 11:07 PM
    0 responses
    305 views
    0 likes
    Last Post CaptainJack  
    Started by Mindset, 04-21-2026, 06:46 AM
    0 responses
    244 views
    0 likes
    Last Post Mindset
    by Mindset
     
    Started by M4ndoo, 04-20-2026, 05:21 PM
    0 responses
    345 views
    0 likes
    Last Post M4ndoo
    by M4ndoo
     
    Started by M4ndoo, 04-19-2026, 05:54 PM
    0 responses
    176 views
    0 likes
    Last Post M4ndoo
    by M4ndoo
     
    Working...
    X