I have a similar report on wowinterface from a person who is not seeing the bug on r279 but is seeing the bug on r280. I can't reliably reproduce it, so it must be something with both of your configurations. Either way, I am in the process of fixing it right now as soon as I can figure out what broke. See if r279 is working fine for you or not.
Parnic, if I have missed, thanks for the great mod, I really can't live without it (believe me I have tried) ;)
After I have found that removing some addons doubled my fps before, I'm strictly examining them now (60+ addons) and doing performance checks on a weekly basis. Sadly IceHUD is on the top currently and actually every hud using dogtags stays there too (just for reference yesterday I tried one without - DHUD and could not even find it on the list). Since IceHUD outputs just several static values, have you though in the direction of removing it?
LibDogTag is a completely optional library. If you delete anything with LibDogTag in it from the IceHUD\libs directory (and make sure that no other mod is loading it...), the mod will continue to function but not look quite as pretty. In addition, if you use the console command "/console predictedPower 0", you can shave a lot of time off the mana bars since they will fall back to the old event-based mana/energy regen behavior instead of the new update-every-frame behavior that Blizzard added in 3.0. Note that that console command will effect even the blizzard UI (and probably other addons) since it's a console command supplied by Blizzard and not me.
It's also worth noting that IceHUD's values are far from "static." They're quite the opposite, actually. The purpose of the HUD is to constantly monitor the state of the player and whatever he's targeting and to make sure that the information displayed is accurate and up-to-date. Those values are about as dynamic as you can get unless you're just standing around in a capital city doing nothing.
Out of curiosity, what are you using to test performance?
Thanks Parnic. I'm using PerformanceFu as OptionHouse was not updated. I have removed the 2 dogtags libs and from a first glance (and a test fight) I can't see any difference in the display, still works perfect. The addon, however went from being N1 in the list to between 14th and 17th position. It surely made a difference ;) CurseUpdater will do me a great favor of swiftly adding the libs back on next update so can there be made an option if to use dogtags or not? I have tried the console option but other than the energy of my rogue went the old way, no visible performance gains.
And sorry for my l2engish problem, by "static" I meant not that values itself are static, but their format and what they show. Take for example DaHud, it makes extensive usage of dogtags, every label, every value in there is an editable dogtag and I have used that to create few bars/labels in the past
Edit: well I saw what is missing without dogtags, the target frame :(
Thanks for the build Parnic, but that option does not disable dogtags. True, it does something in that direction, IceHUD went from being leader to 2nd-3rd place with it off, but I still can do /dogtag and see the help. Tried again, removing it places it on ~15th position. The error related to the missing dogtags is fixed tho and target frame fully visible ;)
Err, /dog is a console command that is triggered by any addon loading LibDogTag, not just IceHUD. I will continue to investigate performance of IceHUD using this option versus removing the library completely, but the presence of /dog does not mean that IceHUD is still using dogtags. You reloaded the ui after un-checking the box, right?
Hello! Thanks for a great addon! I have found a bug - when I use a macro to activate a trinket and then cast a spell the cast bar does sometimes not show up. If I just cast the spell without the macro it works as intended. Can you please fix this? :)