Elitist Jerks - View Single Post

Meloeth · 06/03/08, 1:55 PM

I hosted a new version of the addon on Curse.com, the new version should no longer screw up other addons such as damage meters and SCT. I also fixed some bugs that caused somone at hull health to sometimes show as having less then full health as well as making sure periodic heals and damage shield damage got registered by the addon.
I havn't had time to throughly test these changes so I can't say for sure everything works correctly now but I sure hope so!

@ Daboran
Yes, it would be possible to make the addon affect only specific addons by requiring these addons to register for the faster health updates. This would mean though that any and all addons that wanted to receive faster health updates would need to make changes in their addons. The idea with this design of the addon is to replace the the built-in function with a better version that works exactly the same in every way (which the last version didn't, but the new one hopefully does!).

@ Polleke
Somehow I got it into my head the UNIT_HEALTH event was called HEALTH_UPDATE yesterday afternoon/evening, I'll blame the heat for that!

And yes, you are right about the performance, it's far more important to look at the CPU usage for this addon then at the memory usage. When testing the CPU usage of the addon itself it was low, but I haven't throughly tested the extra CPU usage for other addons which might go up quite a bit depending on what they do when receiving a UNIT_HEALTH event. If performance proves to be a major issue I might have to either add a option to limit the health update speed somewhat or rethink the design of the addon and require other addons to register for the faster health updates to receive them.

06/03/08, 1:55 PM	#44 (permalink)
Meloeth Glass Joe Meloeth Night Elf Druid The Maelstrom (EU)	I hosted a new version of the addon on Curse.com, the new version should no longer screw up other addons such as damage meters and SCT. I also fixed some bugs that caused somone at hull health to sometimes show as having less then full health as well as making sure periodic heals and damage shield damage got registered by the addon. I havn't had time to throughly test these changes so I can't say for sure everything works correctly now but I sure hope so! @ Daboran Yes, it would be possible to make the addon affect only specific addons by requiring these addons to register for the faster health updates. This would mean though that any and all addons that wanted to receive faster health updates would need to make changes in their addons. The idea with this design of the addon is to replace the the built-in function with a better version that works exactly the same in every way (which the last version didn't, but the new one hopefully does!). @ Polleke Somehow I got it into my head the UNIT_HEALTH event was called HEALTH_UPDATE yesterday afternoon/evening, I'll blame the heat for that! And yes, you are right about the performance, it's far more important to look at the CPU usage for this addon then at the memory usage. When testing the CPU usage of the addon itself it was low, but I haven't throughly tested the extra CPU usage for other addons which might go up quite a bit depending on what they do when receiving a UNIT_HEALTH event. If performance proves to be a major issue I might have to either add a option to limit the health update speed somewhat or rethink the design of the addon and require other addons to register for the faster health updates to receive them.