Announcement

Collapse
No announcement yet.

setDefaultBarBgColor() does not work correctly in esignal 1086

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

  • setDefaultBarBgColor() does not work correctly in esignal 1086

    I just installed esignal 1086 and found out setDefaultBarBgColor() does not work correctly in esignal 1086. It seems it completely hides the candlestick bars so that the charts become unvisible.

    Testing script and screenshot are attached. Look at the most left of the screenshot and only the left half part of the first bar is visible, which is another problem of setDefaultBarBgColor as in old esignal version (it sets bg color from the middle of current bar to the middle of the next bar instead of from the middle of two bars.

    - Clearpicks




    var d, d1;
    var indexBgColor;

    function preMain()
    {
    setPriceStudy(true);
    }

    function main()
    {
    if ( getBarState() == BARSTATE_ALLBARS ) {
    indexBgColor = true;
    }

    if ( getBarState() == BARSTATE_NEWBAR ) {
    var d = day(0);
    if ( d != d1 ) {
    d1 = d;
    indexBgColor = ! indexBgColor;
    if ( indexBgColor == true ) {
    setDefaultBarBgColor(Color.RGB(200, 200, 200));
    }
    else {
    setDefaultBarBgColor(Color.lightgrey);
    }
    }
    }
    }
    Attached Files

  • #2
    Hello Clearpicks,

    Thank you for reporting your findings. The background coloring z-order issue will be fixed in the next release.

    The coloring from the center of the bar to the center of the next bar is the current design. We'll explore the possibility of changing the juncture to a location between the bars.
    Jason K.
    Project Manager
    eSignal - an Interactive Data company

    EFS KnowledgeBase
    JavaScript for EFS Video Series
    EFS Beginner Tutorial Series
    EFS Glossary
    Custom EFS Development Policy

    New User Orientation

    Comment


    • #3
      Indicators painting over top of price bars

      Jason or anybody at eSignal:
      When will a fix be out for this new bug, it prevents usage of many indicators I use and was going to develop. To me anyway this was a major goof and should be remidied asap.
      Thanks
      Dave

      Comment

      Working...
      X