Border Indicators not working #173


  • Defect
  • Invalid
Closed
Assigned to _ForgeUser117147
  • Forge_User_05913966 created this issue Aug 14, 2010

    What steps will reproduce the problem?
    1. Set up a rapidly changing indicator for border, in this case: "Threat"
    2. Get infight
    3. Get error spammed :/

    What is the expected output? What do you see instead?
    I expect the border to turn red when I have aggro. Instead, it simply stays black and doesn't react to threat changes. Strangely enough, "low mana" indicator seems to work.

    What version of the product are you using?
    Grid2 v528

    Do you have an error log of what happened?
    [13:32:06] [string "return function (self, unit) local count = ..."]:1: attempt to call method 'GetCount' (a nil value)
    [C]: in function `GetCount'
    [string "return function (self, unit) local count = ..."]:1: in function `GetColor'
    Interface\AddOns\Grid2\modules\IndicatorBorder.lua:11: in function `OnUpdate'
    Interface\AddOns\Grid2\GridIndicator.lua:115: in function `Update'
    Interface\AddOns\Grid2\GridStatus.lua:38: in function `UpdateIndicators'
    Interface\AddOns\Grid2\modules\StatusMana.lua:12: in function <Interface\AddOns\Grid2\modules\StatusMana.lua:8>

    Please provide any additional information below.
    I'm using the following priorities: voice > threat > lowmana, all on account level

  • Forge_User_05913966 added the tags New Defect Aug 14, 2010
  • Forge_User_05913966 posted a comment Aug 15, 2010

    Update: After playing for a while, both threat and lowmana borders work - but what triggered this is totally unknown to me. I used Grid2 for a couple of times (w/- and w/o personal settings) and each and every time I would get spammed with this error.

  • _ForgeUser117147 posted a comment Aug 16, 2010

    I have added a check in the code so that this error doesn't occur anymore.

  • Forge_User_05913966 removed a tag New Sep 3, 2010
  • Forge_User_05913966 added a tag Invalid Sep 3, 2010
  • Forge_User_05913966 closed issue Sep 3, 2010

To post a comment, please login or register a new account.