Bartender 4 w/ WoW v.3.2 - New Shaman Totem bar #148


  • Defect
  • Fixed
Closed
Assigned to nevcairiel
  • _ForgeUser2020282 created this issue Jun 30, 2009

    What steps will reproduce the problem?
    1. Login to game and switch to secondary talent spec
    2.
    3.

    What is the expected output? What do you see instead?
    Expected to have bartender action bars wipe clean for dual spec (or if already set up 2nd instance of action bars for 2nd spec, have those talents show up)
    While BT4 does change over accordingly, you also get the top "line" border of the blizz default actionbar1 along with the 4 new "buttons" for the new shaman totems. While playing druid in cat form, the entire actionbar1 + shaman totem buttons shows up.

    What version of the product are you using?
    v4.3.3-8-g9aff89f (released: 2009/05/26)

    Do you have an error log of what happened?
    No errors caught in BugSack

    Please provide any additional information below.
    I am only curious if you are aware of this issue with the new Shaman Totem buttons and are looking into how to cope with BT4. If not aware, wanted to bring to your attention, if aware then I'll just patiently wait ^.^

  • _ForgeUser2020282 added the tags New Defect Jun 30, 2009
  • _ForgeUser2020282 posted a comment Jul 2, 2009
    Here is a screenshot of what it looks like after I change to either my primary or secondary spec: WoW PTR Bartender4 & Default Actionbar As you can see at the bottom there.... over my chat window, I have the 4 shaman totem slots, and below it (as sometimes happens) I have the entire action bar1. Going across the entire screen is the top border of the actionbar1 & 2.
  • zaph0n posted a comment Aug 4, 2009

    Here's the fix...

    diff -rw ./Bartender4/Bartender4.lua /Applications/World of Warcraft/Interface/AddOns/Bartender4/Bartender4.lua
    124a125,128
    > 
    >     hooksecurefunc('TalentFrame_LoadUI', function()
    >         PlayerTalentFrame:UnregisterEvent('ACTIVE_TALENT_GROUP_CHANGED')
    >     end)
    
  • _ForgeUser526267 posted a comment Aug 4, 2009

    Where in the lua file do you apply this fix, Zaphon?

    Could you please elaborate?

    On which line do you add this? do you replace anything?

    I attempted to locate it by searching the file for "hooksecurefunc" The only thing listed was a "MainMenuBar_ToPlayerArt" is your fix added before that? after that? Does it need it's own section created?

    I may sound like a total newb, but once I know where in the file to put your fix I'll be all good.

  • nevcairiel posted a comment Aug 5, 2009

    I applied the fix, but couldn't test it yet due to down servers. Will test and push a new version as soon as the EU server get back online.

  • _ForgeUser301303 posted a comment Aug 5, 2009

    Just to make sure, this bug also occurred with a warrior in my guild. It is not solely with druids. Any switch to a secondary or primary spec produces the Blizzard action bar 1.

    I can post a screenshot if needed, but I did want it known that this bug occurred with other classes.

  • _ForgeUser2020282 posted a comment Aug 5, 2009

    I'm sorry guys, I should have posted here as well. I posted on the WoW.Curse.Com forums for Bartender 4, that this happens with ALL of my characters (Have not tested on Shaman's yet as I have all classes except shamans lol), not just my druid on PTR.

    This problem was still happening on live servers as of Tuesday, August 4th just after the servers came back up (US servers) from the patch around 6:30pm EST. I have just finished updating all 27 addons that needed updating, so I will test again on the live servers right now to see how it goes. Hopefully this new version of Bartender 4 has the fix applied (I do not know where on the .lua file to apply that fix either, zaphon...)

  • _ForgeUser2020282 edited title Aug 5, 2009
  • _ForgeUser2020282 posted a comment Aug 5, 2009

    Ok, BT4 Version 4.3.3-16.g2f8f888 (Released: 2009/08/05) has the fix and can now switch talents without any default bars showing up where they're not supposed to.

    @Zaphon: Sorry man, just realized you put what line on the lua to apply that fix... was hard to see at first ;-) 124a125,128 is where it was lol... my bad! I saw it in the newly updated .lua file to make sure it was there before loading into the game.

    Updating this ticket to show it was fixed (Author, please do the same if possible?)

  • _ForgeUser2020282 posted a comment Aug 5, 2009

    Issue resolved. Update to BT4 v. 4.3.3-16-g2f8f888 (Released: 2009/08/05)

  • nevcairiel removed a tag New Aug 6, 2009
  • nevcairiel added a tag Fixed Aug 6, 2009
  • nevcairiel closed issue Aug 6, 2009
  • nevcairiel posted a comment Aug 6, 2009

    Glad to hear that the fixed worked.


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