DWMend

Cool. Unfortunate that you have to constantly scan now to avoid the bug, but if its the trade off that has to be made to have this work properly, so be it.

But in terms or working properly, version 02_01/02_02 has problems that have prevented me from testing further.
--The download is listed as "02_02" but the download is "DWMendLarge02_01.rar". DWMendLarge.lua has a date/time of 05/07/08, 1:50AM, DWMendLarge.toc is 1:35AM. Minor point: why the name change? The title in the TOC is still "DWMend", which is different than the folder & file names.
--Installing those files, the text is still on the bar(s), not above them as was supposed to happen with v01_06.
--Most seriously, it bugs out when trying to move the bars with the /script DWMEND_Lock() command, unlike v01_0x which could be moved without a problem. Enter that command and the following error is thrown up and the bar refuses to move:

<string>:\"DWMEND_Lock()\":1: attempt to call global 'DWMEND_Lock' (a nil value)\n<in C code>: in function `RunScript'\nInterface\\FrameXML\\ChatFrame.lua:1590: in function `?':\nInterface\\FrameXML\\ChatFrame.lua:2995: in function `ChatEdit_ParseText':\nInterface\\FrameXML\\ChatFrame.lua:2724: in function `ChatEdit_SendText':\nInterface\\FrameXML\\ChatFrame.lua:2745: in function `ChatEdit_OnEnterPressed':\n<string>:\"*:OnEnterPressed\":1: in function <[string \"*:OnEnterPressed\"]:1>

Retry the command, the error repeats. So the bar is stuck in the middle of the screen; disabled it after that. Will do CPU testing & enable the debugging when the bars can be moved again.

Great job on the text on top, will make usability a bit easier .

Latency here to my primary server medians 130ms & rarely exceeds 300ms on a busy night (as in approx. 4 times a month). Of course Blizzard servers have a tendency to lag out on occasion, but the night when the problem occurred there were no latency problems for either myself or anyone else in the raid. I make a habit of checking it before & during important events here (raids, etc.).

For reference, 2 priests in a Kara raid last night and it didn't occur. The bug may (or may not) be connected to the script to make the bars movable; only happened when I executed the script. Small sample size, sure . But its another possibility.

Next time the issue occurs (and latency is fine) I'll edit the timeout in the LUA and have it ready to go for the next raid. Will also experiment with executing the script before the raid starts. Then move onto your "MendBug" if it continues to occur.

When it wasn't showing up at all, the bar didn't show up on the initial POM cast (and all jumps thereafter). And yes, it was for sure cast and jumping . Most future initial casts & jumps caused the bar to appear, but some (approximately 20%) did not.

I didn't record whether it was missing only certain jumps as well. Yes, there was another holy priest in the raid (2 total including me).

Yes, long testing experience here; I always make sure of using the latest version of any mod before filing a report. In this instance, it was the current version "01_05" (DWMend.lua having a file date of 3/31/08 2:25AM). No prior versions were used.

The unfortunate part about this issue is that testing under most all raid scenarios, you very rarely can reproduce exact fighting conditions. Unless you want to lose your place in the raid . Unlike when soloing or in a party with good friends who put up with your mod testing .

The closest inexact outline I can give for reproduction at this time is to do a ZA raid at high speed (going for the first timed chest/boss) on a 70 priest . Memories of the issue first occurring was when casting a POM during the trash killing at the bottom of the first set of stairs going up towards the first boss.

Will give v01_05 one last go during this weekend's raids here. If it repeats (it likely will), I'll post back. Hopefully you will be able to find the issue and eliminate it.

At first glance, this replacement for Mendwatch is terrific. Tested with CPU profiling active (and OptionHouse for measuring CPU/second consumption), DWMend uses 0 CPU time when you are not casting Prayer Of Mending (POM) and very little when you do. Which is great behavior. Prayer Of Mending Tracker, on the other hand, uses a fair bit of CPU continually (even when you are idle) and about 3 times as much as DWMend when you cast POM. Which isn't good behavior .

But some issues with DWMend currently.

--It sometimes "misses" POM being cast by my 70 priest in a raid. During testing last night, it usually picked it up and displayed proper timer bars when POM both was cast & when it jumped to different targets. But approximately 20% of the time, when a new POM was cast on a target (and jumped to other targets), no bars showed up at all.

And yes, POM _did_ land on the first target properly during the times the bars did not appear. Normally you can't recast on a target when they already have a "jumped" POM on them; that wasn't the case with this problem.

This "20%" problem occurred after entering the "/script DWMEND_Lock()" command at the start of the raid so the bars could be moved. Didn't have time to enter it again during the raid to lock the bars.

20% of the time the bars not showing up after a POM being sucessfully cast means this isn't reliable enough currently for raid or instance usage (vs. Prayer Of Mending Tracker which works properly 100% of the time, at least). So hope this problem can be resolved.

--The fonts, bars, alpha level & so on being unable to be adjusted (other than moving them) is also problematic. When a bar overlays the text, the text is barely readable. I have to get close to the monitor and squint. The other raid priests I had testing this mentioned that the text visibility was an issue for them as well.

Only when the bars are close to "empty" can you see the name text underneath clearly. Some adjustments for bar and/or text alpha (and/or color) would help with this issue.

It's so useful to know where your PoM is and how long is left. Then you know when/if you need to cast another. I've been lost without a working one for a while.

Thanks DW! (which, coincidentally, are my initials too ... spooky!)

Is there any way to change the font?

well, maybe it doesn't. and if i don't pay attention to who it bounces to then maybe i don't need it anyway. not like i get credit for the healing.