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 CaptainJack, 05-29-2026, 05:09 AM
    0 responses
    236 views
    0 likes
    Last Post CaptainJack  
    Started by CaptainJack, 05-29-2026, 12:02 AM
    0 responses
    150 views
    0 likes
    Last Post CaptainJack  
    Started by charlesugo_1, 05-26-2026, 05:03 PM
    0 responses
    162 views
    1 like
    Last Post charlesugo_1  
    Started by DannyP96, 05-18-2026, 02:38 PM
    1 response
    243 views
    0 likes
    Last Post NinjaTrader_ChelseaB  
    Started by CarlTrading, 05-11-2026, 05:56 AM
    0 responses
    198 views
    0 likes
    Last Post CarlTrading  
    Working...
    X