Authors CurseForge

how do i move the bars? >.>

/cdt anchor gives me an error

"Interface\FrameXML\ChatFrame.lua:2170:AceConsole-2.0: Option handler "ToggleAnchor" not found.

to be exact :/

I believe you have 2.1 (newest). I'm still using 2.08. I heard some people have problem with /cdt anchor in 2.1. So I download 2.08 and upgrade the lib from svn.wowace.com/files and everything works fine.

whee, i stuck with 2.1, but i copied the libs over from another addon i updated earlier today(since the svn is down apparantly) and it worked :)

Just upped a new version:

2.11
- Updated all Libraries (and therefore hopefully fixed the anchor bug; also included a new SpellStatusLib
which should improve spell detection)

Put it in the SVN?

Quote from Saroz »

Put it in the SVN?

I concur.

Was moving around the bars in v2.11 and crashed WoW. Could be a generic 'move frame' crash but I thought I'd share it.

ERROR #132 (0x85100084) Fatal Exception
Program: F:\Program Files\World of Warcraft\WoW.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 001B:007A2452

The instruction at "0x007A2452" referenced memory at "0x03AC3FE8".
The memory could not be "read".

Krsnik, sorry for the long wait on the check in. I guess MS IExplorer doesnt show me the messages screen in the top right.

Whats CTD and can we have a screenshot in the forst post? wiki maybe?

Moved to Chrono thread

Quote from Industrial »

Whats CTD and can we have a screenshot in the forst post? wiki maybe?

It shows the cooldowns on your spells and looks quite nifty to boot. And unlike the other 2 addons that do the same thing.. this one seems to work without issues, for me anyways.

I got the latest version from the files section.

Really i think we need some basics command (like /cdt lock, /cdt scale, /cdt list of commands like Perfect Raid or oCD) coded into the add on.

Ok, I can use Visor or better edit the options code but reloading the UI every damn time is a pain.

Not many options just the basic ones: movable frame, some scaling and some anchor.

We can easily change the font and the textures but, with many characters, I have customized ui (/cdt profile ? :P).

Just a little Ace style configuration.

Thank you.

Spaming a spell and casting a new spell inbetween still results in no cooldown bar appearing.

I just installed the latest version today to try it out, and as a rogue I hit Sprint. The timer bar was for 5 minutes instead of 5 seconds? The sprint effect had long worn off while the timer bar was still on screen and counting down for another 5 mins.

im pretty sure you cant sprint every 5 seconds, and that the cooldown is 5 minutes, thus your answer

Quote from bugme »

I just installed the latest version today to try it out, and as a rogue I hit Sprint. The timer bar was for 5 minutes instead of 5 seconds? The sprint effect had long worn off while the timer bar was still on screen and counting down for another 5 mins.

bugme your talking about how long the effect lasts. not the cooldown. if you want timer bars for that look into getting Chronometer. tho the effect of sprint lasts 12sec not 5sec =O

I have a problem with disappearing bars once I log out and back in. They seem to be gone out of the visible area (neither /cdt anchor does show anything nor /cdt test). It doesn't seem to save the correct positions (or doesn't position them correctly on log in).

I have the same problem with Chronometer.

Quote from johndoe »

I have a problem with disappearing bars once I log out and back in. They seem to be gone out of the visible area (neither /cdt anchor does show anything nor /cdt test). It doesn't seem to save the correct positions (or doesn't position them correctly on log in).

I have the same problem with Chronometer.

have you tried running it w/o any other mods installed? are you using 2.11?
and do you use !!!Libraries? if so i'd disable it, or update it to the renamed version !!!Libs
it was causing problems w/ candybars. but that doesn't explain why the bars are moving around. just sounds like you have some old libs floating around.

also did you use CooldownTimers v1xx? i don't know if it has SaveVariable problems with the old one. i know they use the same folder

First: Please put CDT up on the SVN!

Quote from elvendawn »

have you tried running it w/o any other mods installed? are you using 2.11?
and do you use !!!Libraries? if so i'd disable it, or update it to the renamed version !!!Libs
it was causing problems w/ candybars. but that doesn't explain why the bars are moving around. just sounds like you have some old libs floating around.

I tracked down the problems to the SnapToGrid addon which is totally odd. If I use it to place the anchor CDT doesn't write the correct y value into the saved variables files.

I'm at a total loss here why this is the case because SnapToGrid worked and works with every other addon I used and use. It shouldn't make any difference if I manually move the anchor to a place or use SnapToGrid (which only provides 'snapping' to an imaginary grid) to do that. On the screen it looks like the exact same position (and I'm totally convinced it is). However, I think on logout sth happens what should not happen (the bars work totally fine after placing the anchor using SnapToGrid as long as I don't log out).

Further investigations show what happens:

• Manually placing: CDT writes a correct (negative) y value into the saved variables file
• SnapToGrid placing: CDT writes an incorrect (positive) y value (and thus placing the bars outside of the visible screen)

The anchor was placed in both cases at the same spot and SnapToGrid was loaded both times, too.

Somehow when it comes to take the current bar placing and writing them into the saved variables files CDT fucks up - that's my conclusion. But why does it only fuck up when placed with the help of SnapToGrid? It even doesn't fuck if I first SnapToGrid place and then minimally nudge the anchor manually.

Any ideas? :s

My wild guess is that the culprit is in these lines of code: (Lines 778-823 of CooldownTimers.lua)

-- Creates the anchor frames
function CooldownTimers:CreateAnchor(text, cRed, cGreen, cBlue)
	local f = CreateFrame("Button", nil, UIParent)
	f:SetWidth(200)
	f:SetHeight(25)
	
	f.owner = self
	
	if self.db.profile.barposition.x and self.db.profile.barposition.y then
		self:RestorePosition(f, self.db.profile.barposition.x, self.db.profile.barposition.y) 
	else
		f:SetPoint("CENTER", UIParent, "CENTER", 0, 50)
	end

	f:SetScript("OnDragStart", function() this:StartMoving() end )
	f:SetScript("OnDragStop",
		function()
			this:StopMovingOrSizing()
			local x, y = self:GetPosition(this)
			this.owner.db.profile.barposition.x = x
			this.owner.db.profile.barposition.y = y
        end)

	f:SetBackdrop({bgFile = "Interface/Tooltips/UI-Tooltip-Background",
                                            edgeFile = "Interface/Tooltips/UI-Tooltip-Border",
                                            tile = false, tileSize = 16, edgeSize = 16,
                                            insets = { left = 5, right =5, top = 5, bottom = 5 }})
	f:SetBackdropColor(cRed,cGreen,cBlue,.6)
	f:SetMovable(true)
	f:RegisterForDrag("LeftButton")

	f.Text = f:CreateFontString(nil, "OVERLAY")
	f.Text:SetFontObject(GameFontNormalSmall)
	f.Text:ClearAllPoints()
	f.Text:SetTextColor(1, 1, 1, 1)
	f.Text:SetWidth(200)
	f.Text:SetHeight(25)
	f.Text:SetPoint("TOPLEFT", f, "TOPLEFT")
	f.Text:SetJustifyH("CENTER")
	f.Text:SetJustifyV("MIDDLE")
	f.Text:SetText(text)
	
	f:Hide()

	return f
end

That would at least explain why Chronometer suffers from the same problem - it uses the exact same code (apart from some variable names).