Those of you with these "phantom bars" on your target frames - do you happen to have the Bar Fader module enabled on the affected frames? If so, can you try disabling it for a little while to see if the problem goes away?
Shamans also had significant changes to their buffs/debuffs. The aura filters will be updated closer to WotLK release (once the spells are no longer constantly changing). In the meantime you can either disable the aura module or, if you're willing to get your hands dirty, try and manually edit the filter list.
Just FYI, Pitbull is bugged for rogues in WOTLK beta. Both for energy ticks and for combo points.
Works perfectly for my 78 DK though.
Wasn't sure where to report these issues.
The combo points should be working now - Shefki made a few changes to make that code WotLK-compatible (though I believe he was testing on a druid in cat form, it should be the same for rogues). Can you describe the "bugged" behavior in more detail?
I just recently switched from using DHUD and Pitbull to just using Pitbull, with the Player and Target frames moved around to replace the HUD style I prefer so much. Problem is, I don't know of any way to make those 2 frames click-through, which causes frustrations when I'm moving the camera around.
Does Pitbull support making frames click-through? Failing that, is posting in this topic sufficient for suggesting the feature?
No. PitBull is a unit frame addon; unit frames by definition can be clicked to target the unit, as well as setting the mouseover unit while your cursor is over them. HUDs, because they are designed to be right in your face, generally just use regular click-through frames to avoid getting in the way.
Also, anyway to get Bugsack/Buggrabber to give me the same error frames or text output that Swatter does?
I've committed a few more TotemTimers tweaks to try and prevent your error; however, I wasn't able to reproduce it myself on a shaman. If you are still having issues, there are a few things you may need to try: disabling OmniCC to verify that it's not an addon conflict, deleting PitBull_AltAura (it's no longer needed, and if you have an old copy of it lying around, there is some potential for stray bugs), and lastly giving me some more information about the conditions/steps to reproduce the error.
[2008/07/15 19:27:22-578-x1]: PitBull-3.0r78449\PitBull.lua:812: Usage: PitBullTexture26:SetDrawLayer("layer")
PitBull-3.0r78449\PitBull.lua:5066: in function `object_method'
LibRockTimer-1.0-1118 (FuBar):289: in function <...Ons\FuBar\libs\LibRockTimer-1.0\LibRockTimer-1.0.lua:227>
Boo. Can you list the modules you're running, particularly any that are class-specific or not included in the default PitBull package?
This looks like taint from another addon that's being blamed on PitBull. Try disabling PitBull and using your macro in combat, and disable whichever addon gets blamed then. Repeat until the error stops popping up - the last addon you disabled was the culprit.
Hmm....I tried that, and got a bunch of options but nothing for the cast bars. Anywhere else I should be looking?
Are you looking for the bar or the texts? From your description it sounds like the bars were showing up fine, but the texts may have been accidentally disabled. To re-enable them, go to Target -> Texts -> Other, and in the Disabled Texts dropdown click "Cast" and "CastTime".
Hey guys, quick question and possibly very easy to solve, but I've been having some problems with my target's unit frame cast bars. I believe someone has also mentioned it but it was addressed. On my target's cast bar, it is only showing an icon and then the cast bar, but no text, I looked in the menu under the texts on target but there was no option for the cast bars, only combat and other. Any suggestion on this would be great. I've downloaded quartz for the time being to try and fix it but I'm not a huge fan of the cast bars and would love to have them on the targets frame instead. Any and all help is greatly appreciated. Thx.
To see all options for your target frame you will need to either target something or use a config mode.