• If this is your first visit, you will have to register before you can post. To view messages, please scroll below and select the forum that you would like to visits. Questions? Be sure to check out the Forum FAQ.

Announcement

Collapse
No announcement yet.

Partner 728x90

Collapse

Visible click not Working

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

    Visible click not Working

    Dear Support,

    The "Visible" option in Indicators Properties does not work for indicators that place buttons in the main toolbar, such as draw objects.

    There are several ToolBar Button indicators in the forum that you can test (ToolBarClock, ToggleTrades V1.0, , ToolBarButtonExample, etc. After unchecking the "Visible", the indicator remains visible.

    Thanks.

    #2
    Hello,

    Thank you for the post.

    Yes more advanced GUI items would not be Rendered so the standard Visibility would not apply in these situations. In this case, the developers of those items could implement hiding logic for their buttons using the IsVisible property of the indicator. But this would also require that they check for this value to change somehow which may take more resources/effort on their part.

    Here is one example of how this could be checked, depending on when the item adds the GUI elements this may need to be modified:

    Code:
    else if (State == State.DataLoaded)
    {
    	Print(IsVisible);
        if(IsVisible)
        {
             //add gui
        } else {
            //make sure gui is removed
        }
    }
    I look forward to being of further assistance.
    Last edited by NinjaTrader_Jesse; 05-03-2017, 07:28 AM.
    JesseNinjaTrader Customer Service

    Comment


      #3
      Originally posted by NinjaTrader_Jesse View Post
      Hello,

      Thank you for the post.

      Yes more advanced GUI items would not be Rendered so the standard Visibility would not apply in these situations. In this case, the developers of those items could implement hiding logic for their buttons using the IsVisible property of the indicator. But this would also require that they check for this value to change somehow which may take more resources/effort on their part.

      Here is one example of how this could be checked, depending on when the item adds the GUI elements this may need to be modified:

      Code:
      else if (State == State.DataLoaded)
      {
      	Print(IsVisible);
          if(IsVisible)
          {
               //add gui
          } else {
              //make sure gui is removed
          }
      }
      I look forward to being of further assistance.
      Thank you Jesse,

      This seems odd, a feature either works for all indicators or not since we do not know what is "more advanced GUI."

      Another case in example is when the same toolbar buttons indicators are loaded, if one attempts to create a (any) Market Analyzer indicator column the program will crash and closed with an "Unhandled" condition error. A strange behavior suggesting that MA can not handle "more advanced GUI" either.

      The work around in this case was to uninstall such toolbar indicators before one can create a Market Analyzer column for another indicator (i.e., RSI, etc.). This should not be necessary.

      Thanks.

      Comment


        #4
        Hello,

        Unfortunately, we cannot control what modifications third parties may make to the overall chart GUI, these items are not something that could be controlled internally like the plots of an Indicator.

        This would strictly be up to the developer to make sure their custom GUI elements work as expected as they are in complete control of adding/removing/creating that element. This also includes changing tabs, opening indicator menus, reloading the chart etc.. there are quite a few steps in making a new GUI element and also making it work like it was a native item created by NinjaTrader.

        As far as the Market Analyzer and the crash, this would be a situation where you know a specific cause which you could bring to the attention of the developer of that item. It is likely that the item is using something from a Chart specifically which the MarketAnalyzer would not have. There are certainly cases where a developer creates an item with a chart in mind but then that same item will not work in other places where they had not tested it.

        To know the script is in the MarketAnalyzer to change logic to allow it to work, the developer could look into using the following condition:

        Code:
        if (Parent is MarketAnalyzerColumnBase)
        	Print("Running on a Market Analyzer");
        In general, if you are running into a problem with a specific item you import, in most cases you would need to contact the developer of that item to report that you're having problems running it in that specific situation. We have some guidelines on items that can affect performance and steps you can take here: http://ninjatrader.com/support/helpG...tallingAdd-Ons

        Please let me know if I may be of further assistance.
        JesseNinjaTrader Customer Service

        Comment

        Latest Posts

        Collapse

        Topics Statistics Last Post
        Started by xsgex, Yesterday, 09:46 PM
        0 responses
        2 views
        0 likes
        Last Post xsgex
        by xsgex
         
        Started by Steve L, Yesterday, 09:36 PM
        0 responses
        1 view
        0 likes
        Last Post Steve L
        by Steve L
         
        Started by krugman25, Yesterday, 09:34 PM
        0 responses
        4 views
        0 likes
        Last Post krugman25  
        Started by indy73, Yesterday, 04:42 PM
        0 responses
        15 views
        0 likes
        Last Post indy73
        by indy73
         
        Started by Italianforex, Yesterday, 06:20 AM
        2 responses
        13 views
        0 likes
        Last Post gplatis
        by gplatis
         
        Working...
        X