• 0

    posted a message on [Grid] Feature possibility inquiry
    Not feasible, as people outside your group don't have "permanent" unit ids (they may have transient ones, but those aren't suitable).
    Posted in: AddOn HELP!
  • 0

    posted a message on Grid
    Quote from Greltok
    Most importantly, unit buttons aren't being created on PTR. I haven't had chance to figure out why yet.


    This is because SecureGroupHeaderTemplate's initialConfigFunction behavior changed. I'm still trying to grok the changes.
    Posted in: Grid & Grid2
  • 0

    posted a message on Grid
    Quote from Greltok
    GridRange has some issues with tooltip scanning using LibGratuity-3.0 on the PTR.


    The issue is that SetSpell() was renamed to SetSpellBookItem(). This will require a fix to LibGratuity-3.0.
    Posted in: Grid & Grid2
  • 0

    posted a message on Grid
    Checked in a fix for GridStatusAuras.

    I have GridStatusHeals ready to go using the new Blizzard healing API. I just have to decide when to commit it, as it doesn't work on live.

    GridRange has some issues with tooltip scanning using LibGratuity-3.0 on the PTR.

    Most importantly, unit buttons aren't being created on PTR. I haven't had chance to figure out why yet.
    Posted in: Grid & Grid2
  • 0

    posted a message on Grid
    Quote from Fonex
    GridStatusAuras is failing to scan any buffs or debuffs due to the auto-detection of the abolish spells (Disease and Curse). Both of these are gone in 4.0 + (and from what I've read unlikely to return).


    I installed the PTR last night, and noticed this as well. I will compare our changes, and check in a fix later.
    Posted in: Grid & Grid2
  • 0

    posted a message on Grid
    Quote from Stanzilla
    and rangecheck seems to have a problem with the player, I'm always out of range of myself!


    I'm not seeing this. Can you send me your saved variables?
    Posted in: Grid & Grid2
  • 0

    posted a message on For cataclysm - automatic role tagging
    This is already fairly trivial using LibGroupTalents-1.0. See GridStatusRole.
    Posted in: Addon Ideas
  • 0

    posted a message on Grid
    Quote from Stanzilla
    I can't seem to get rid of this background here, background color is set to black with alpha 0.


    Fixed in r1336.
    Posted in: Grid & Grid2
  • 0

    posted a message on Grid
    Quote from Greltok
    Is this a regression from Ace2 Grid?


    Sorry, it is a regression.
    Posted in: Grid & Grid2
  • 0

    posted a message on Grid
    Quote from Stanzilla
    I can't seem to get rid of this background here, background color is set to black with alpha 0.


    Is this a regression from Ace2 Grid?

    I don't think it's currently possible to remove that background through the UI.

    From GridLayout.lua:
    -- create bg texture
    f.texture = f:CreateTexture(nil, "BORDER")
    f.texture:SetTexture("Interface\\ChatFrame\\ChatFrameBackground")
    f.texture:SetPoint("TOPLEFT", f, "TOPLEFT", 4, -4)
    f.texture:SetPoint("BOTTOMRIGHT", f, "BOTTOMRIGHT", -4, 4)
    f.texture:SetBlendMode("ADD")
    f.texture:SetGradientAlpha("VERTICAL", .1, .1, .1, 0, .2, .2, .2, 0.5)
    Posted in: Grid & Grid2
  • 0

    posted a message on Grid
    Quote from MSaint
    Second, in the latest version, Grid errors out when loading, at least for me, apparently because after the self.name:match in the modulePrototype:onInitialize method, module.name is empty for the first round of modules (GridLayout, etc.). Actually, the fix for this that I used to get things going was simply to change references to module.name where I didn't want the long version to module.moduleName, to which AceAddon DOES NOT prepend the parent name and underscore. At least, this can be used for creating the namespaces so that they match the old system (for the debug options name and text I used module.moduleName or module.name).


    The module name is now pulled from moduleName. Thanks for the tip.

    Quote from MSaint
    I hope I'm being more helpful than I am bothersome.


    The more eyes on it, the better.
    Posted in: Grid & Grid2
  • 0

    posted a message on Grid
    Quote from Stanzilla
    The border and background color pickers under the layout options are not working properly.)


    Thanks for the report. Fixed in r1327.
    Posted in: Grid & Grid2
  • 0

    posted a message on Grid
    Quote from MSaint
    I was able to fix this by changing GridCore.lua...

    Quote from MSaint
    I also found that GridStatusHealth.lua...


    Thanks for the report. Fixed in r1326.
    Posted in: Grid & Grid2
  • 0

    posted a message on LibTalentQuery-1.0
    Quote from starlon
    I've been using this library in my tooltip addon since BC, and it's always done this. Sometimes, and most of the time while in a raid, it doesn't pull up the talents no matter how long I wait. I'm likely "doing it wrong" or something.


    When I've seen this issue, it's been due to other AddOns also inspecting using their own system, and rescanning too often. If two or more scans are "in flight" at once, LTQ must assume the resulting talent read is bad, and thus it will discard it and re-queue the scan.

    Check to see if you have other AddOns that call NotifyInspect(). If so, you could try disabling them to see if the problem persists. I've found that RaidBuffStatus (an otherwise very useful AddOn) can cause talent scan stalls if its option to scan weapon buffs is turned on, so I've turned that option off.

    Alternately, see if another AddOn using LTQ has issues. You could try Utopia or Grid+GridStatusRole. Note that these use LibGroupTalents-1.0, a very useful companion library that uses LTQ for its queueing.
    Posted in: Libraries
  • To post a comment, please or register a new account.