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?
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. =)
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:
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...
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!)
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! :)
0
Confirmed: uncommenting them fixed the issue (which only became apparent if you closed via the [X]; using the assigned hotkey worked as expected.)
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?
0
Here's a pastey of the .diff: nQuestLog-r59668:Bindings.xml fix
Cheers!
0
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):
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
0
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:
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...
0
Quick-fix is to open LootLink.lua to line 2596 (in the version I'm using) and look for code like this:
Update it to look like this:
That fixed my LootLink issues.
Now to work out what the heck is causing the MainMenuBarBagButtons nonsense... *sigh*
0
Yup: http://www.wowinterface.com/downloads/fileinfo.php?id=4455
0
Haven't played a warrior using it, but it might help...
0
You said everything I might've thought of and more. :?
0
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!)
0
Me too, hehheh! :wink:
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! :)
0
Regardless.... you suit your name, bro. :P *grin*