just updated from svn.wowace.com and seeing:
MrPlow\MetrognomeLib.lua:141: attempt to call global `print' (a nil value)
---
MrPlow\MetrognomeLib.lua:168: attempt to call global `print' (a nil value)
---
[edit: that would be revision 7 with periodic table revision 64]
just updated from svn.wowace.com and seeing:
MrPlow\MetrognomeLib.lua:141: attempt to call global `print' (a nil value)
---
MrPlow\MetrognomeLib.lua:168: attempt to call global `print' (a nil value)
---
[edit: that would be revision 7 with periodic table revision 64]
Strange. I've turned off the debugging in the MetroGnome lib, so reget that file and try again.
Technically "print" -should- be a global, since it's like... I dunno the default method for LUA =P
Technically "print" -should- be a global, since it's like... I dunno the default method for LUA =P
I used print countless times before I switched to AceDebug for messages. The code looks right, I don't see where an error could be generated. Unfortunately I didn't have time yesterday to try and track down the source of the error.
No errors with the new version.
[edit] I believe I found the source of the problem, the author of TrainerSkills appears to have used "print" as a global variable in his AddOn. My opinion of such code will be left to your imagination.
Thanks again for the quick response and apologies for the extra work done for no purpose.
[edit] I believe I found the source of the problem, the author of TrainerSkills appears to have used "print" as a global variable in his AddOn. My opinion of such code will be left to your imagination.
Thanks again for the quick response and apologies for the extra work done for no purpose.
Whereabouts in TrainerSkills is this definition? I'm not sure what version I should be looking at, as it appears that others are also getting this error...
To be honest, I tossed it after seeing "if (print) then" lines inside a toggle function (for the minimap button?) without doing a more through check. Do a search for "print" and you should find it easily enough.
I think it was within the single function and it may be that just renaming the variable will take care of the problem. But I have trust issues with people who use reserved function names as variables even if it turns out they are local only.
If I were a forgiving sort I wouldn't be a good warlock. :) I may not have the dps down properly but I've got a excellent hold on the insanity.
To be honest, I tossed it after seeing "if (print) then" lines inside a toggle function (for the minimap button?) without doing a more through check. Do a search for "print" and you should find it easily enough.
I think it was within the single function and it may be that just renaming the variable will take care of the problem. But I have trust issues with people who use reserved function names as variables even if it turns out they are local only.
If I were a forgiving sort I wouldn't be a good warlock. :) I may not have the dps down properly but I've got a excellent hold on the insanity.
hum. The function definition for that code is
function TrainerSkillsMinimapButton_Toggle(print)
So wouldn't that make this version of 'print' a local? And not overwrite the global reference?
I really have no clue as to why the error would occur... (I can't actually replicate the issue, however...)
Now that is worrisome. The repair utility says my files are fine. Which implies either the repair utility isn't checking everything or it's a system dependent bug. (WinXPpro sp2 updated, the latest security fixes this week, .Net framework 2)
I'd moved AddOns and WTF into \tmp. Then extracted LuaSlinger. Went into game and typed "print("hello world")" into the script pane and hit execute. I couldn't think of a simpler test that should isolate it.
New version up on SVN, on request by Thiana, there is now bankstacking.
There are three levels, toggleable with the /mp bankstackstyle command
Level 1- Fill stacks in your bank
Level 2 -Level 1 and fill empty slots in your bags (but only for items in that bag)
Level 3 -Level 2 and also use any other free space
This does take into account special bags, and will not try to fill them with nonspecial stuff.
On an inside note, I've removed the dependancy for PT and shifted it into MrPlow as an Embedded library.
I just saw the update in this thread. I'm short on time, but a first test with my priest worked without a problem. So it seems you didn't break anything at least ;) .
Great :). I've been thinking about a 'priority' category, and instead came up with a 'disregard' one, in that it works in the opposite way. You specify items that MrPlow will ignore, and he'll then move everything else around the items specified. That way you can place them wherever in your bags you want, and unless you move them, they'll always stay where they are. It's a little easier to implement than a priority one, and also gives the opportunity to order them as the user wants.
Great :). I've been thinking about a 'priority' category, and instead came up with a 'disregard' one, in that it works in the opposite way. You specify items that MrPlow will ignore, and he'll then move everything else around the items specified. That way you can place them wherever in your bags you want, and unless you move them, they'll always stay where they are. It's a little easier to implement than a priority one, and also gives the opportunity to order them as the user wants.
Okay, Version 4 is up on the SVN, I'll leave it there for a bit for you people to play around with, before upping it to WoWi.
new commands: /mp ignore [add|del|clear]
you can see what you've got in the list with
/mp report
and either shiftclick from the report or from your inventory.
Thanks for the quick reply!
MrPlow\MetrognomeLib.lua:141: attempt to call global `print' (a nil value)
---
MrPlow\MetrognomeLib.lua:168: attempt to call global `print' (a nil value)
---
[edit: that would be revision 7 with periodic table revision 64]
Strange. I've turned off the debugging in the MetroGnome lib, so reget that file and try again.
Technically "print" -should- be a global, since it's like... I dunno the default method for LUA =P
I used print countless times before I switched to AceDebug for messages. The code looks right, I don't see where an error could be generated. Unfortunately I didn't have time yesterday to try and track down the source of the error.
No errors with the new version.
[edit] I believe I found the source of the problem, the author of TrainerSkills appears to have used "print" as a global variable in his AddOn. My opinion of such code will be left to your imagination.
Thanks again for the quick response and apologies for the extra work done for no purpose.
Whereabouts in TrainerSkills is this definition? I'm not sure what version I should be looking at, as it appears that others are also getting this error...
To be honest, I tossed it after seeing "if (print) then" lines inside a toggle function (for the minimap button?) without doing a more through check. Do a search for "print" and you should find it easily enough.
I think it was within the single function and it may be that just renaming the variable will take care of the problem. But I have trust issues with people who use reserved function names as variables even if it turns out they are local only.
If I were a forgiving sort I wouldn't be a good warlock. :) I may not have the dps down properly but I've got a excellent hold on the insanity.
hum. The function definition for that code is
function TrainerSkillsMinimapButton_Toggle(print)
So wouldn't that make this version of 'print' a local? And not overwrite the global reference?
I'm going to try without any addons but luaslinger and see if print still works without error.
Why in the world would blizzard disable print?
Please double check me, I hope I'm wrong.
Now that is worrisome. The repair utility says my files are fine. Which implies either the repair utility isn't checking everything or it's a system dependent bug. (WinXPpro sp2 updated, the latest security fixes this week, .Net framework 2)
I'd moved AddOns and WTF into \tmp. Then extracted LuaSlinger. Went into game and typed "print("hello world")" into the script pane and hit execute. I couldn't think of a simpler test that should isolate it.
New version up on SVN, on request by Thiana, there is now bankstacking.
There are three levels, toggleable with the /mp bankstackstyle command
Level 1- Fill stacks in your bank
Level 2 -Level 1 and fill empty slots in your bags (but only for items in that bag)
Level 3 -Level 2 and also use any other free space
This does take into account special bags, and will not try to fill them with nonspecial stuff.
On an inside note, I've removed the dependancy for PT and shifted it into MrPlow as an Embedded library.
Can y'all give it a go and see if it falls over?
I'm all for that!
new commands: /mp ignore [add|del|clear]
you can see what you've got in the list with
/mp report
and either shiftclick from the report or from your inventory.
It handles multiple items as well.
Great job Wob!!