Added T10 2 piece Resto Druid and T10 2 piece Holy Paladin in the alpha build, I'm 99.99% sure the Druid one works, but a Paladin with T10 2 piece who could double check that it works would be great.
I fixed an outstanding bug where GUIDs with \249\250-255 "naturally" would cause errors when decompressing, this will cause a small incompatibility with older versions because it'll compress \249 to stop the bug from happening. From a database I gathered of 410 GUIDs (player/pet/npcs) FE was only used 7 times, so the impact overall should be rather small and won't cause hard errors.
Message: Interface\AddOns\LibHealComm-4.0\LibHealComm-4.0.lua:1013: attempt to compare number with table
Time: 01/21/10 13:57:15
Stack: [C]: ?
Interface\AddOns\LibHealComm-4.0\LibHealComm-4.0.lua:1013: in function <Interface\AddOns\LibHealComm-4.0\LibHealComm-4.0.lua:989>
Interface\AddOns\LibHealComm-4.0\LibHealComm-4.0.lua:2281: in function `?'
Interface\AddOns\LibHealComm-4.0\LibHealComm-4.0.lua:2700: in function <Interface\AddOns\LibHealComm-4.0\LibHealComm-4.0.lua:2699>
[2010/01/30 15:52:09-3434-x33]: LibHealComm-4.0-53 (!Libs):1120: attempt to call global 'UnitHasVehicle' (a nil value)
LibHealComm-4.0-53 (!Libs):2282: in function `?'
LibHealComm-4.0-53 (!Libs):2705: in function <Interface\AddOns\!Libs\LibHealComm-4.0.lua:2704>
Happens when i cast Prayer of Healing on a Raidgroup.
I normally play as holy spec on my priest, but recently I've changed from shadow to disc as my offspec.
I can't say I've noticed it before but using v1.6 of LibHealComm-4.0 I am not seeing the incoming penance heals as expected.
When I target myself I only get 1 tick as incoming heals (approx 3k) that is cleared after the first tick hits, the 2nd and 3rd tick have no associated incoming heal value.
When I target someone else I only get 2 ticks as incoming heals (approx 6k) that decreases as each tick hits, the 3rd tick has no associated incoming heal value.
Does this happen for anyone else?
edit: It looks like travel time may be a factor. when I lag a bit and cast on myself then I get an incoming heal value of approx 6k, but it gets reduced to 3k when the first tick hits which is almost instant. I would still expect the last tick to be shown as incoming heals though.
While I understand what you are saying, something just didn't 'feel' right about the incoming heals on penance.
To test it out I recorded a video of a penance cast with the combat log showing to see the sequence of events.
When casting on a friendly NPC I saw this sequence:
Ah I see what you are saying, you are counting the instant heal as a tick.
 Yea, you're right. Basically, the channel starts and then ~0.02 seconds later the "instant" tick happens so locally you get 3 ticks. I changed it so locally, Penance is 3 ticks and comm-wise it's still 2 ticks. The addon comm message should always arrive after the first "instant" tick.
I've had some reports that at least some incoming heals are not showing in VisualHeal. Tonight i did a little bit of testing myself, and i could verify this. A little debugging and i found the cause.
This is the (simple) setup: A priest heals me. I have LHC4 and the wrapper running (no LHC3). The Priest has LHC3, LHC4 and the wrapper. The priest casts flash heal on me. I can see in my addon message monitor that i get both LHC3 and LHC4 messages. I also see the event HealComm_HealStarted triggered. Following on into the update code, i have these lines to get the amount of incoming heal on the player specifically:
local incomingHeal = self.HealComm:GetOthersHealAmount(self.PlayerGUID, self.HealComm.CASTED_HEALS);
local nextTime, nextGUID, nextSize = self.HealComm:GetNextHealAmount(self.PlayerGUID, self.HealComm.CASTED_HEALS, nil, self.PlayerGUID);
Now, incomingHeal is set to an appropriate value (around 4500), but nextTime is nil. That's not supposed to happen, afaik, right?
Having the library share your data with others even if you aren't using the data shared by others is the whole point of LibHealComm. The resources used by the library are so insignificant that there is no way it could have a noticable impact on the performance of any machine capable of playing WoW even on minimum settings.
The only possible reason I can think of to install it and then disable it is to be a douche and annoy the other healers in your group. Especially now that nearly every unit frame addon in existence supports LibHealComm, healers come to rely on being able to see at least who is being healed, and it's extremely annoying to be grouped with someone who doesn't have the library.
If you don't want users of your addon sharing their heal data with their group, don't embed LibHealComm, and tell them if they want to see heals from other people they have to install the library separately. I doubt many of them will thank you for it. Are there really users who complain about having LibHealComm sending comms and actually have some factual basis for their complaints, rather than just vague whining from a position of total ignorance?
I know this is a fairly old post to reply to, but an [admittedly cursory] look didn't turn up one point, which is that while the ideal of having LHC function whether the user running it wants to use its information or not is laudable, in reality a lot of people are using LHC when they have no business using it at all - there are a ton of raid frames and unit frames that embed it, and the majority of players using these are not healers. They transmit nothing of value, and other than a handful of people (some raid leaders, some good tanks) do nothing useful with received values either, even if their raid frames/unit frames are displaying incoming heals.
All of my raiding characters are DPS - I will never hold off using a healthstone because I see an incoming heal on myself. The addons I use should most certainly provide an option to at least unregister from incoming LHC events. Sure, you can argue that in the grand scheme of things, processing LHC messages isn't much of a performance hit, but the point is that for likely the majority of people currently running LHC, it's an unnecessary operation. I could run a mod that counts the number of times I strafe left each week at no noticeable performance cost too, but that has no value to me, so if some mod I downloaded had an embedded library to do so, I would want to disable it. The addons I use that include LHC fortunately do contain options to disable display of incoming heals (although they're vague enough in their wording that I don't know if they just hide the display or actually unregister the events) - authors of addons that aren't guaranteed to be used ONLY by people who actually want to see incoming heals or actually have outgoing heals should continue to provide options to disable use of LHC by non-healers.