Announcement

Collapse
No announcement yet.

Partner 728x90

Collapse

Indicator inputs corrupted

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

    Indicator inputs corrupted

    Do you know what would cause this to happen?

    The inputs look like this on two PCs
    Click image for larger version

Name:	zul01.png
Views:	1
Size:	25.9 KB
ID:	900738

    But for everyone else they look like this
    Click image for larger version

Name:	zul02.png
Views:	1
Size:	21.7 KB
ID:	900739

    These are the input declarations in the code
    Click image for larger version

Name:	zul03.PNG
Views:	1
Size:	4.6 KB
ID:	900740

    I've tried uninstalling/reinstalling. But it keeps coming back, and it's on two PCs.

    Any help greatly appreciated.

    Happy New Year!

    #2
    We don't support dynamically adding different data series but I'm still happy to assist. Likely you will need to make the input and enum and cast it to PeriodType.

    Again not supported but something like this should work:

    Code:
    public enum TrendPeriodType
    	{
    		Minute = PeriodType.Minute,
    		Day = PeriodType.Day,
    		Week = PeriodType.Week,
    		Month = PeriodType.Month,
    		Year = PeriodType.Year
    	}
    [Description("")]
    [GridCategory("Your category")]
    	[Gui.Design.DisplayName("Period Type")]
    	public TrendPeriodType STrendType
    {
        get { return sTrendType; }
        set { sTrendType = value; }
    }
    Then when adding in initialize()
    Code:
    Add((PeriodType)STrendType, STrendValue);
    Let me know if I can further assist.
    LanceNinjaTrader Customer Service

    Comment


      #3
      Hi Lance,

      Thanks for your quick reply. I'm not sure if what you've given me is different from what I already have.

      The variables I have are
      private PeriodType symbolbartype = PeriodType.Day; // Default setting for symbolname1
      private int symbolinterval = 1; // Default setting for symbolname1

      Then in Initialize I have
      Add("$AUDCAD", symbolbartype, symbolinterval);

      Then the inputs I have are
      [Description("Symbol bar type")]
      public PeriodType SymbolBarType
      {
      get { return symbolbartype; }
      set { symbolbartype = value; }
      }

      [Description("Symbol bar interval")]
      public int SymbolBarInterval
      {
      get { return symbolinterval; }
      set { symbolinterval = value; }
      }


      What you're saying is that I should declare a separate enum (different from PeriodType) and then cast using PeriodType. So...

      public enum TrendPeriodType
      {
      Minute = PeriodType.Minute,
      Day = PeriodType.Day,
      Week = PeriodType.Week,
      Month = PeriodType.Month,
      Year = PeriodType.Year
      }

      private TrendPeriodType symbolbartype = TrendPeriodType.Day; // Default setting for symbolname1
      private int symbolinterval = 1; // Default setting for symbolname1


      Add("$AUDCAD", (PeriodType)symbolbartype, symbolinterval);


      [Description("Symbol bar type")]
      public TrendPeriodType SymbolBarType
      {
      get { return symbolbartype; }
      set { symbolbartype = value; }
      }

      [Description("Symbol bar interval")]
      public int SymbolBarInterval
      {
      get { return symbolinterval; }
      set { symbolinterval = value; }
      }

      Is there any fundamental difference between what I have and what you have? Specifically, do you think the differences in the code above would cause the issue I am seeing? This code is installed on hundreds of PCs and I don't understand how it is only causing a problem on two.

      Thanks
      Last edited by bubblegum; 01-02-2014, 09:18 AM.

      Comment


        #4
        In terms of coding I don't see a difference, however in terms of values being properly serialized I see that using public PeriodType SymbolBarType may be causing issues.

        Neither method is supported but trying the enum and then casting would be my first attempt to fix the issue.
        LanceNinjaTrader Customer Service

        Comment


          #5
          OK. I'll try that. Thanks.

          Comment


            #6
            FYI it seems the customers had messed around with their instrument settings and deleted some required symbols. Putting the symbols back has solved the problem.

            Comment

            Latest Posts

            Collapse

            Topics Statistics Last Post
            Started by GLFX005, Today, 03:23 AM
            0 responses
            1 view
            0 likes
            Last Post GLFX005
            by GLFX005
             
            Started by XXtrader, Yesterday, 11:30 PM
            2 responses
            11 views
            0 likes
            Last Post XXtrader  
            Started by Waxavi, Today, 02:10 AM
            0 responses
            6 views
            0 likes
            Last Post Waxavi
            by Waxavi
             
            Started by TradeForge, Today, 02:09 AM
            0 responses
            13 views
            0 likes
            Last Post TradeForge  
            Started by Waxavi, Today, 02:00 AM
            0 responses
            3 views
            0 likes
            Last Post Waxavi
            by Waxavi
             
            Working...
            X