Authors CurseForge

Quote from Silvaristiar »

In Cartographer.lua around line 305

These lines were commented out:

WorldMapFrameCloseButton:SetScript("OnClick", function()
ToggleWorldMap()
end)

They aren't commented out in older versions. Maybe he is working on a change. I uncommented the lines and it fixed this.

Confirmed: uncommenting them fixed the issue (which only became apparent if you closed via the [X]; using the assigned hotkey worked as expected.)

Also noted at line 393

self:AddSecureHook(WorldMapFrame, "Show", "WorldMapFrame_Show")

The w of the first show wasn't showing up in some of my editors. It showed up in ConTEXT. Don't know if this contributed to any problems.

Checked this in a hex editor: both are the same code, internally. Must be something corrupted on your side. Check the file inside the .zip that you downloaded?

Hola, Quag. =) Found an oopsie via FrameXML.log and fixed it locally but I don't have auth to commit it (or TSVN is screwing with me again :-P).

Here's a pastey of the .diff: nQuestLog-r59668:Bindings.xml fix

Cheers!

Quote from OrionShock »

i don't use LootLink but i had a different problem
<SNIP>
Deleted those lines out and my errors went away, it dosn't appear to brake any functionality.

That'll get rid of the errors, yes, but it doesn't fix the problem. :(

If you open your OBB and try to move items around, their border hilights will update but not the textures.

I managed to fix (hack? :P) this in the OneBank\OneBank.lua file at around line 113 by adding a call to the new BankFrameItemButton_Update() function that Blizzard added (as a replacement to the now-missing *OnUpdate() function):

	if not self.frame.bags[-1].colorLocked then
		for k, v in ipairs(self.frame.bags[-1]) do 
			self:SetBorderColor(v)
			BankFrameItemButton_Update(v)
		end
	end

It's definitely nothing more than a temporary hack, I think, as that loop seems to only run when the bag in question isn't "colorLocked" but it works for me, for now. I'll definitely be glad when an official fix is available. =)

Use that "fix" at your own risk! :o

Quote from Trapspringer »

For any and every item I mouseover in OneBag, I get the following error -- which isn't really telling me which mod/library could be at fault...very odd error.

[2007/09/25 19:34:11-419-x11]: Interface\FrameXML\MainMenuBarBagButtons.lua:82: Usage: GameTooltip:SetOwner(frame):
Interface\FrameXML\MainMenuBarBagButtons.lua:82: in function `BagSlotButton_OnEnter':
<string>:"*:OnEnter":2: in function <[string "*:OnEnter"]:1>

Again, caused by Bliz updating their _OnEnter() syntax; this time, in their function in MainMenuBarBagButtons.lua.

The fix is to update OneBag\templates.xml on line 57 so that the code looks like:

	<OnEnter>
		OneBag:HighlightBagSlots(this:GetID()-19)
		BagSlotButton_OnEnter(self)
	</OnEnter>

I'd submit that to the SVN myself but a) I don't know if anyone other than Kaelten can do that and b) I don't like submitting changes to other peoples' addons without asking first, anyway. ;)

Hope that helps, though. Still trying to track down that pesky BBankFrameItem bug...

Quote from Trapspringer »

Add info -- figured it out, it's Telo's Lootlink causing these issues.

It's LootLink's _OnEnter() function causing problems as it's not been updated to use the new 'self' parameter.

Quick-fix is to open LootLink.lua to line 2596 (in the version I'm using) and look for code like this:

function LootLink_ContainerFrameItemButton_OnEnter()
	LootLink_AutoInfoOff();
	lOriginal_ContainerFrameItemButton_OnEnter();

Update it to look like this:

function LootLink_ContainerFrameItemButton_OnEnter(self)
	LootLink_AutoInfoOff();
	lOriginal_ContainerFrameItemButton_OnEnter(self);

That fixed my LootLink issues.

Now to work out what the heck is causing the MainMenuBarBagButtons nonsense... *sigh*

Quote from "Sirian" »

Quote from "Myrathi" »

...TTSpellTimer...

Hmm, can't find a mod by that name on any of the normal mod sites... You have a link? :P

Yup: http://www.wowinterface.com/downloads/fileinfo.php?id=4455

It's not an Ace mod but could TTSpellTimer possibly help with what you're wanting?

Haven't played a warrior using it, but it might help...

To Rowne: In short? Agreed.

You said everything I might've thought of and more. :?

Quote from "Gazramon" »

Note, I am finding that most MODS will start working if you just change the interface # in the .TOC file to "10900", but there is always a chance that there will be additional problems.

This can never be stressed enough: you should never "just change the interface #" to the new value to get someone else's mod to work. Ever. That's what the tickbox at the top of the "AddOns" dialog is for, off the char-select screen: it bypasses interface# version checking and lets all the addons work anyway!

As you said: there's always a chance that there will still be additional problems; but if you update the interface#, then you have the additional issue of remembering which addons are really up-to-date and which you've just arbitrarily faked!

You don't need to update it yourself. Ever. So please: just don't do it. Leave interface# updation to the mod's author(s)? It's really not worth the grief.

(and I would really, really, REALLY love to stab whoever started that craze in the face with a rusty spork!)

Quote from "tekkub" »

I'd love to be able to harass Rowne ^^

Me too, hehheh! :wink:

Quote from "tekkub" »

Anywho, anyone got a good guild that will take a semi-RPer and his friend. We're not hardcore RP but we'll do our best to stay IC. We're really looking more for a great group of people to be with than anything else.

And I concur -- what server and side (A/H) are you guys playing on? Most all of my old gamer buddies are moving away from WoW and the guilds I was in have all but evaporated :(. I play both UK -and- US servers, so um... either works! :)

*flick* *flick* *flick* Heh. The Mysticalgirl thing happens to me quite frequently (though, different people). :roll:

Regardless.... you suit your name, bro. :P *grin*