This would show the elite/rare-coloured borders in the style you choose in the Target frame options, also allowing you to turn it off for certain target types, (Target, Target's Target, Focus, Focus' Target,) individually.
Of course, if you don't feel completely comfortable messing around in the file, hopefully the fix will be noticed on the bugtracker soon, and become part of a new release in short order.
Safe journeys,
Llyrwech
Could this be used to put in a custom texture to show on elites/rares, such as the original gold/gray dragons? Would I just store the texture in the SharedMedia folder and call it in the PitBull lua?
Fine, but there is no option to hide the default blizz-buff-frames!?
Beside this, is there a way to change the style of the duration, e.g. "4:59" and not like "5m"
Since one of the updates, Pitbull's main module is actually crashing the game on login / ui reload. Turning the module off solves the problem; When the module is on, the crash happens not always.
I was getting crashes upon login today so i started to switch off Addons... PB is the one causing my crashes apparently. In fact the modules that are causing my game to crash are: Experience, Health, Highlight and InteractLines. All of them individually trigger the crash.
EDIT: Actually i -think- i just solved my problem. Deleted Pitbull and updated manually without using aceupdater.
I was having this same issue. I crashed nearly every time I logged into WoW so I disabled every addon and enabled them one by one to target the issue. The issue was indeed related to Pitbull, but I did the same thing and manually updated w/o using Ace updater. Everything worked fine ever since.
The odd thing is that I can use ace updater on my laptop with the same addons installed and I've never crashed. I am assuming its some type of ace updater bug?
Since one of the updates, Pitbull's main module is actually crashing the game on login / ui reload. Turning the module off solves the problem; When the module is on, the crash happens not always.
I was getting crashes upon login today so i started to switch off Addons... PB is the one causing my crashes apparently. In fact the modules that are causing my game to crash are: Experience, Health, Highlight and InteractLines. All of them individually trigger the crash.
EDIT: Actually i -think- i just solved my problem. Deleted Pitbull and updated manually without using aceupdater.
I was having this same issue. I crashed nearly every time I logged into WoW so I disabled every addon and enabled them one by one to target the issue. The issue was indeed related to Pitbull, but I did the same thing and manually updated w/o using Ace updater. Everything worked fine ever since.
The odd thing is that I can use ace updater on my laptop with the same addons installed and I've never crashed. I am assuming its some type of ace updater bug?
So now am sure yes its Pitbull :( did the same one by one. By reloading or getting ingame error132 back and without Pitbull after long /reloadui spam and logging coming back ingame didnt got that crash anymore.
Guess maybe a problem with 3D models or still Aura module or somethg gonna do more test.
Since one of the updates, Pitbull's main module is actually crashing the game on login / ui reload. Turning the module off solves the problem; When the module is on, the crash happens not always.
I was getting crashes upon login today so i started to switch off Addons... PB is the one causing my crashes apparently. In fact the modules that are causing my game to crash are: Experience, Health, Highlight and InteractLines. All of them individually trigger the crash.
EDIT: Actually i -think- i just solved my problem. Deleted Pitbull and updated manually without using aceupdater.
I was having this same issue. I crashed nearly every time I logged into WoW so I disabled every addon and enabled them one by one to target the issue. The issue was indeed related to Pitbull, but I did the same thing and manually updated w/o using Ace updater. Everything worked fine ever since.
The odd thing is that I can use ace updater on my laptop with the same addons installed and I've never crashed. I am assuming its some type of ace updater bug?
So now am sure yes its Pitbull :( did the same one by one. By reloading or getting ingame error132 back and without Pitbull after long /reloadui spam and logging coming back ingame didnt got that crash anymore.
Guess maybe a problem with 3D models or still Aura module or somethg gonna do more test.
Just delete all the Pitbull folders and reinstall the add-on. It worked for me, no more crashes.
X-perl's healthbar would change color at 20%. I know you can set it to change color at 50%, but can you change that to 20% (or any other value for that matter)?
Could this be used to put in a custom texture to show on elites/rares, such as the original gold/gray dragons? Would I just store the texture in the SharedMedia folder and call it in the PitBull lua?
Not easily. Yes, it would be possible to add the dragon borders to the border selection list. In SharedMedia-1.0.lua, you'd find the code:
Unfortunately, the method for drawing the border around the unit frames produces a less -than-desirable outcome. A new drawing method would have to be written into the code of PitBull.lua. However, since I typically use WowAceUpdater, I'd rather not have to make all these adjustments every time I update. Best would be to make this a feature request on the bugtracker and hope CK decides to add it to the official releases. ^_~
Hey, I'm glad the crit error issue has been fixed and also it shows the text on bars again. great!
however I found one little issue with the player unitframe and petframe. they both don't fade when I'm out of combat. they only fade for a short duration (1-2 secs) right after doing a reload or a login. target and ToT are working fine. any ideas?
After reading reports about Aura being problematic, I've taken a look at it. There was indeed quite some room for improvements.
I've attached a patch of what I finally got to. The CPU usage of UpdateBuffs() and UpdateDebuffs() has been drastically reduced, using a few tricks.
I've tested it a bit, and there shouldn't be any change in behaviour, appart from a slight bug corrected regarding setHighlightColor() in the option table.
is evil but with target frame not beig drawn proprly or at all fixed? im afraid of updating pitbull :)
It's not that the target frame is improperly drawn. It looks fantastic, as does the rest of the add-on. All I was saying is that the draw method is not set up for applying the Dragon-style borders to the target frame. Trust me, there's nothing at all wrong with the appearance of the add-on. It's sleek and attractive.
After reading reports about Aura being problematic, I've taken a look at it. There was indeed quite some room for improvements.
I've attached a patch of what I finally got to. The CPU usage of UpdateBuffs() and UpdateDebuffs() has been drastically reduced, using a few tricks.
I've tested it a bit, and there shouldn't be any change in behaviour, appart from a slight bug corrected regarding setHighlightColor() in the option table.
Alright, I went through it, changed some stuff around and such, hopefully it's quite a bit more efficient now.
After reading reports about Aura being problematic, I've taken a look at it. There was indeed quite some room for improvements.
I've attached a patch of what I finally got to. The CPU usage of UpdateBuffs() and UpdateDebuffs() has been drastically reduced, using a few tricks.
I've tested it a bit, and there shouldn't be any change in behaviour, appart from a slight bug corrected regarding setHighlightColor() in the option table.
Works great so far CK, freeze and spike during raids are gone using Aura module. Still that huge spike when you leave Combat, ie: whn Boss die specially and abit less on Thrashes.
But as i said its just to let you known coz i dont care much about it thats not those annoying spikes/freezes during a fight^^
Loving using Pitbull back withh all his functionality.
Alright, I went through it, changed some stuff around and such, hopefully it's quite a bit more efficient now.
Still that huge spike when you leave Combat, ie: whn Boss die specially and abit less on Thrashes.
I'm thinking about some addon that would call erroneously (or not) AceEvent's ScheduleLeaveCombatAction(). I've no idea about PitBull, but that looks like a possible reason.
I'll add an audit hook to my installation, just to see if something's going on.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Could this be used to put in a custom texture to show on elites/rares, such as the original gold/gray dragons? Would I just store the texture in the SharedMedia folder and call it in the PitBull lua?
Yes check out Buffalo or Buffalo2
I was having this same issue. I crashed nearly every time I logged into WoW so I disabled every addon and enabled them one by one to target the issue. The issue was indeed related to Pitbull, but I did the same thing and manually updated w/o using Ace updater. Everything worked fine ever since.
The odd thing is that I can use ace updater on my laptop with the same addons installed and I've never crashed. I am assuming its some type of ace updater bug?
So now am sure yes its Pitbull :( did the same one by one. By reloading or getting ingame error132 back and without Pitbull after long /reloadui spam and logging coming back ingame didnt got that crash anymore.
Guess maybe a problem with 3D models or still Aura module or somethg gonna do more test.
Just delete all the Pitbull folders and reinstall the add-on. It worked for me, no more crashes.
Thanks1
Not easily. Yes, it would be possible to add the dragon borders to the border selection list. In SharedMedia-1.0.lua, you'd find the code:
border = { ["None"] = "Interface\\None", ["Blizzard Dialog"] = "Interface\\DialogFrame\\UI-DialogBox-Border", ["Blizzard Tooltip"] = "Interface\\Tooltips\\UI-Tooltip-Border", },and change it to:
border = { ["None"] = "Interface\\None", ["Blizzard Dialog"] = "Interface\\DialogFrame\\UI-DialogBox-Border", ["Blizzard Tooltip"] = "Interface\\Tooltips\\UI-Tooltip-Border", ["Dragon Elite"] = "Interface\\TargetingFrame\\UI-TargetingFrame-Elite", ["Dragon Rare"] = "Interface\\TargetingFrame\\UI-TargetingFrame-Rare", },Unfortunately, the method for drawing the border around the unit frames produces a less -than-desirable outcome. A new drawing method would have to be written into the code of PitBull.lua. However, since I typically use WowAceUpdater, I'd rather not have to make all these adjustments every time I update. Best would be to make this a feature request on the bugtracker and hope CK decides to add it to the official releases. ^_~
Safe journeys,
Llyrwech
Ah, was wondering if there was a way to do it within Pitbull. No, then?
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumhowever I found one little issue with the player unitframe and petframe. they both don't fade when I'm out of combat. they only fade for a short duration (1-2 secs) right after doing a reload or a login. target and ToT are working fine. any ideas?
thank you for another fine release ck, i love it!
I've attached a patch of what I finally got to. The CPU usage of UpdateBuffs() and UpdateDebuffs() has been drastically reduced, using a few tricks.
I've tested it a bit, and there shouldn't be any change in behaviour, appart from a slight bug corrected regarding setHighlightColor() in the option table.
It's not that the target frame is improperly drawn. It looks fantastic, as does the rest of the add-on. All I was saying is that the draw method is not set up for applying the Dragon-style borders to the target frame. Trust me, there's nothing at all wrong with the appearance of the add-on. It's sleek and attractive.
~Llyrwech
German Client PitBull - Already at rev 37823 - Skipping
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAlright, I went through it, changed some stuff around and such, hopefully it's quite a bit more efficient now.
I'm thinking about some addon that would call erroneously (or not) AceEvent's ScheduleLeaveCombatAction(). I've no idea about PitBull, but that looks like a possible reason.
I'll add an audit hook to my installation, just to see if something's going on.