====================
This is a fix for DoTimer by Asheyla:
http://www.wowinterface.com/downloads/info5302-DoTimer.html

As soon as Asheyla posts an update to his addon, I will delete this project.

I'm sure that Asheyla will eventually get around to applying corrections to DoTimer. In the meanwhile, there are some annoying glitches with the current DoTimer, most of which have been caused by changes in World of Warcraft. I think it is important to note that most of the problems users are experiencing with DoTimer are a result of changes to WoW - not bugs in DoTimer.

1- The recent addition of three Shaman spells which cast four totems simultaneously.

3- "You are not in a party" spam. Many addons are causing this problem; DoTimer is one of them. Not everyone will experience this issue, but if you are, this FanFix version of DoTimer corrects it. If you still get the spam with this version of the addon, the problem is being caused by one of your other addons. You might want to grab this addon, which suppresses the problem:http://www.wowinterface.com/download...APartyFix.html

4- A bug in DoTimer related to profile handling.

I wish to note that I did not generate any of the fixes for DoTimer. All four fixes were made by other people. I just applied all the fixes, tested them thoroughly to be sure they work and do not cause problems of their own, and then packaged them for upload here. I give credit to:
----------
**Farmbuyer of wowinterface.com for the Shaman totem fix and the profile fix.**
**cynergy of curse.com for the Hunter trap fix.**
**coani of wowinterface.com for the "You are not in a party" spam fix.**
----------

As soon as Asheyla posts an update to his addon, I will delete this project.

2009-10-19.01
Added the "You are not in a party" spam fix. Which I somehow neglected to apply to the earlier versions. Thank you, coani.

2009-10-14.01
1- Added a fix for profile management errors. Thank you, Farmbuyer.
2- Changed the .toc files as follows:
2a- Changed Interface to 30200 (applied to both .toc files for DoTimer and DoTimer_Options).
2b- Added a note about this "FanFix" version of DoTimer (applied to both .toc files for DoTimer and DoTimer_Options).
2c- Changed the version to 4.3.6f02 (applied to the .toc file for DoTimer only).

Originally posted by Miletus I recently changed some raid frames and need to move my cooldown anchor to one side. I tried unchecking the "Locked" box under Cooldowns Anchor but was still unable to move the anchor. Is there another setting somewhere?

It's possible that you have your cooldown timers appearing under a different anchor. Try unlocking your other anchors - one of them is going to be the anchor you are attempting to move.

You might find it a good practice to trip a few cooldowns so that some timers are running under the anchor you wish to move. I find that having live, active timers makes it easier to position anchors - much better than using the Preview function.

Thanks for keeping this alive; I've been using DoTimer for a year or so and it helps my healing so much.

I recently changed some raid frames and need to move my cooldown anchor to one side. I tried unchecking the "Locked" box under Cooldowns Anchor but was still unable to move the anchor. Is there another setting somewhere?

Originally posted by Akumasama I'm sure it has already been asked but just in case let me ask again. Does this fan-fix includes the Shaman "drop down 4 totems" fix? I had to fix this manually on the lua some months ago.

Yes. That's described on the "Addon Info" tab of this project. And one of the screenshots shows a Shaman with four totems down using one of those spells, with DoTimer correctly displaying a timer for each of the four totems.

The testing I've performed so far has not generated any problems. So to the best of my ability to determine, the 2009-10-19.01 version of DoTimerFanFix is working fine with the WoW 3.3 patch. I therefore will not be issuing an update at this time. Remember to check the box to enable "Load Out Of Date Addons" at the addon management window of the character selection screen.

I did only the most minimal testing in groups, so it is possible that something related to being in a group will need to be addressed.

This project will be updated for 3.3 if any changes are needed. I have not yet had an opportunity to log in to run tests. I anticipate that I'll be able to do so no later than Monday, so look for an update on 14 Dec or 15 Dec - or a post here stating that an update isn't necessary, or that I can't provide needed repairs.

Also please continue to follow the DoTimer project page, as hopefully Asheyla will reappear soon.

------------------------------

I am looking for a little help from someone who is raiding and PvPing: Please use the latest version of DoTimer (from this project, DoTimerFanFix) while in a group and while in a battleground (perhaps in Wintergrasp, too). Then please report here if you receive "You are not in a party" spam or if undesirable timers appear outside of your control. I will try to run this test myself, but I would like to get input from others as I have not experienced this error myself when I have performed testing in the past.

I'm sorry, but I will not be adding any features to DoTimer. I am simply collecting bug fixes, applying them, testing them thoroughly to be sure the fixes don't cause problems of their own; and then posting the updated files as this project. I have no intention of "taking over" DoTimer – I'm simply making a fully-functional version available while Asheyla is on hiatus and not posting bug fixes in response to changes made to the game.

I expect that Asheyla will return, eventually. He has been "counted out" many times in the past, and then come back just as DoTimer users were about to despair that the addon had been abandoned. So please post any feature requests at Asheyla's DoTimer page here:

Originally posted by JMHammer This is something you should take up with Asheyla when he returns from his hiatus, because what you are experiencing is due to the way DoTimer attempts to prevent "spamming" your interface with undesirable or unneeded timers ...

Ok was wondering if it was a bug or was working as intended. Thx JM. i'll definately as Asheyla about it when he gets back.

The word "Cooldowns" in your screenshot is the name of the anchor. All you have to do is tell DoTimer to hide the anchor name - there is no need to edit the addon's files.

Go here:
Interface Options->Addons->DoTimer Anchors->Cooldowns Anchor

Now look in the configuration pane to the right for GROUP NAMES in white text. In that section you will find an option to enable or disable DISPLAY NAMES.

Un-check the box to the left of the words DISPLAY NAMES.

-----

I suggest you save your current profile, then make a new profile to use for testing purposes. You'll be amazed at all the things you can do with DoTimer - it can take the place of 10 other addons. But there are SO many options that the only way to learn to use them all is to experiment with the addon and play with the various options.

This is something you should take up with Asheyla when he returns from his hiatus, because what you are experiencing is due to the way DoTimer attempts to prevent "spamming" your interface with undesirable or unneeded timers.

As you noted, if you select a unit as your target, or as your focus, or if you mouseover that unit; DoTimer will track your DoTs on that unit by putting up a timer for each one.

Units that are not your target or focus or mouseover yet happen to become affected by one of your DoTs - such as when a Death Knight spreads his diseases to a group via Pestilence - will generally not produce a timer unless you happen to mouse over that unit, or that unit is in direct combat with you.

In my opinion - and it's only my opinion - I think that it's better for DoTimer to behave in this way, as it prevents the screen from being filled with a huge number of timers in most AoE situations. It can STILL fill your screen in certain AoE situations if you don't explicitly set a limit on the number of timers that can be displayed at one time; but thanks to the built-in filtering, it doesn't happen very often.