Party 1 Pet Health Bar doesn't seem to be updated.
It always stays at 100%(full) even though the pet was taking damage.
- Registered User
Member for 11 years
Last active Fri, Oct, 4 2013 14:32:22
- 0 Followers
- 214 Total Posts
- 0 Thanks
Jun 5, 2008Posted in: General AddOnsQuote from Elarenda »
Will give this addon a poke tomorrow :)
Bargos has my vote.
The name has "Bar" so it would indicate that the addon is an Action Bar addon.
The -gos part could be attributed to Bongos, Bongos2 and Bongos3. To me, an addon with -gos I think of Tuller. :D
Apr 29, 2008Posted in: General AddOnsQuote from avazza »
If their rectangular it's probably Zuaxana's Model Citizien, which by the way kinda brings me to my feature request. Any chance to be able to set the width and hight of the "portrait area" or whatever its called? :)
If I had that function I could switch from Zuaxanas, this mod is so much better in many ways.
I've asked Benumbed about this also, and the response was that it was becoming troublesome if the Height <> Width.
Apr 25, 2008Maybe that's the setting I needed to change... FrameStrata or FrameLevel?Posted in: General AddOns
The portraits are indeed blank/black. I would change the settings. It would be good for that session.
Switching to different characters, the settings are kept, but, the portraits are blank again. But, I could have sworn that at one point, the class icon did appear after logging on the first time.
Apr 23, 2008DaHud (Revision 71116):Posted in: General AddOns
No errors in BugSack during the time I played. However, the portraits are all blank (Player, Pet, Target and Target-of-Target). I tried setting them and after I set it, portraits were ok.
But, I switched characters and the portraits are back to blank again. I might have to -ahem- start from scratch and set it up all again as a last resort.
Apr 22, 2008DaHud r70821Posted in: General AddOns
I've been getting this error.
[2008/04/22 10:45:39-295-x4]: DaHud\plugins\Buffs\LargeSelfBuffs.lua:147: DaHud_buff1_Buff5:SetPoint(): DaHud_buff1_Buff6 is dependent on this DaHud\plugins\Buffs\LargeSelfBuffs.lua:147: in function `?' DaHud\modules\Buffs\Core.lua:392: in function `UpdateFrame' DaHud\modules\Buffs\Core.lua:212: in function <Interface\AddOns\DaHud\modules\Buffs\Core.lua:197> ---
Apr 22, 2008I too used the old version of DaHud (the one prior to 2.4 options) and plus the default settings of that version was to my liking.Posted in: General AddOns
But, I've moved on to the latest version and took the time to adjust my bars/icons/buffs. Now, my UI is better than the old version. :)
I also added the following optional libs: Threat-2.0 and LibRangeCheck-2.0. Both can be found in files.wowace.com.
These libs fixed my problem about no range values and the threat error that I've been getting.
Check if there are any addon updates on other addons you have that uses the same libraries DaHud is using.
Apr 21, 2008Posted in: General AddOnsQuote from Benumbed »
Also, you will get "WorldFrame" on anything created in DaHud unless "interactive" is checked. This will enable mouse and allow you to get the name for that frame, just turn it "interactive" off afterwards if you do not want it on.
Thanks for the suggestion.
Apr 21, 2008Posted in: General AddOnsQuote from Chmee »
IMO, when an addon author updates the toc to indicate compatibility with a given version of WoW, he is certifying that he has tested his addon under that version, and that (absent minor, non-fatal errors, perhaps) it works. I haven't written any addons, but I have been a programmer, and I know that, for me at least, the only thing in programming that I like less than testing is documentation. After all, how to use the software I write should be intuitively obvious to anyone with a brain, should it not? And when writing software, there's no need to test it, because I don't make misteaks. :-)
Anyway, my point is that if the addon author isn't willing to make that certification (after all, all addons are "beta" software) then he is right not to update the toc.
Documentation: Yes, it really is a nasty thing to write documentation for a given program. As any change to the actual program, the documentation becomes outdated. And there is always no time to write good documentation.
Outside of "cosmetics", I always test my code especially if I'm moving from one coding scheme to another. The "degree" of testing is another matter though. :) Besides, I don't make algorithm/logic mistakes. The syntax is my only problem. :D
Apr 21, 2008Posted in: General AddOnsQuote from Benumbed »
Will check on the bugs reported in the next day, and have them fixed. Rather busy last few days, sorry =\
No problem, Benumbed.
Any suggestions on how I can "export" my DaHud/DaPortraits settings to another computer.
Will copying the SavedVariables Lua file adequate?
Apr 21, 2008Posted in: General AddOnsQuote from razoon »
Will there be timers on the buff/debuffs? Atleast I dont see them on poison debuffs.
Another thing (same as Ringleron): The buffs/debuffs keep resetting to Large each time I log into the game. Hopefully it can be fixed.
Also, I am not sure as what names I should use for anchors.
For example: what name should I use if I want to anchor to the Player Portrait?
I've been using:
Not entirely sure if /dump is a standard WoW command. I was told it was an Ace2 thing.
Just have to make sure the frame is visible. And if you are getting "WorldFrame", you'll have to dig through the WoW XMLs.
I usually have DaPortraits loaded as well, and I anchor the DaHud Bars/Buffs/Icons to each DaPortraits frame (i.e. DaPortrait_player, DaPortrait_party1, etc). I'm pretty sure frame names are CASE-SENSITIVE.
Lastly, you'll have to "unlock" the DaPortraits for the MouseFocus to have something to focus on. :)
Apr 21, 2008Benumbed:Posted in: General AddOns
I found a possible problem.
In all of the buffs/debuffs I have, I turned off the "Large Self Buffs".
I logged out, switched to a different character, logged back in and all of the Large Self Buffs are all checked again. AFAIK, I'm not using any personal profile as I wanted all characters to have roughly the same HUD settings.
Apr 21, 2008I learned that when it comes to dealing with textures (.blp), you'll have to RESTART WoW for the textures to get loaded.Posted in: General AddOns
Say you started WoW already and copied the textures into your \Interfaces\AddOns\MyAddOn\Textures folder. Then programmed your addon to read the custom texture you just copied. While it will save the setting as designed by the addon's author, the image of the texture will not appear as the texture is not loaded by that WoW client session.
Apr 18, 2008This one is a different error:Posted in: General AddOns
[2008/04/18 09:26:24-281-x1]: DaHud\plugins\Buffs\LargeSelfBuffs.lua:147: DaHud_buff1_Buff5:SetPoint(): DaHud_buff1_Buff6 is dependent on this DaHud\plugins\Buffs\LargeSelfBuffs.lua:147: in function `?' DaHud\modules\Buffs\Core.lua:392: in function `UpdateFrame' DaHud\modules\Buffs\Core.lua:212: in function <Interface\AddOns\DaHud\modules\Buffs\Core.lua:197> <in C code>: in function `TargetUnit' <string>:"TARGETSELF":4: in function <[string "TARGETSELF"]:1> ---
So far I had no errors when I logged into my Warrior.
Then I leveled.
I targeted myself and the above error appeared in my bugsack.
Apr 17, 2008Posted in: General AddOnsQuote from Benumbed »
Large Self Icons are an option, which will enlarge buffs/debuffs cast by you. Still unsure exactly what caused the error, try to reproduce it if you can. If you can reproduce it again, tell me exactly what you did and what buff/debuff number it took to cause it. Also what do you have the max aura's and columns set to?
No problems with checking the Configuration Mode.
If memory serves, I didn't check the Large Self Buffs. But, now, all of my buffs/debuffs have that option check which explains the large icon.
At this time, no errors in BugSack.
I targeted myself (a Priest). The Target of Target portrait that I had configured as "Flat" shows a blank box, but, the Target Portrait is correctly displaying the Priest Class Icon.
I unchecked the Large Self Buffs and the buff/debuff icons were like what I had.
Sadly, I can't reproduce the error. It was when I was buffing/debuffs that I was getting the errors.
I was in my Warrior at the time and was doing Demoralizing Shout. I'll see if I can reproduce it with my Warrior class.
- To post a comment, please login or register a new account.