Our records show that you have outstanding author rewards points. Please confirm your latest payment information and redeem your points balance via the Author Reward Store.
I am having the same problem since the patch. I am running XP not Vista. I have done all the standard trouble shooting. I have even updated my video driver. Some things seem to work like Gatherer, but Cartographer, Auctioneer, WIM, WTN, do not work. I have uninstalled and tried Carbonite and it does not work. I too am a premium member but as I stated befor since the patch many addons do not work even though Curse says that the all are up to date. IF ANYONE knows what to do PLEASE LET ME KNOW!!!???!?!?!?
Do you have "load out of date addons" checked on the character select screen?
Just go to the Localization pages of the Babble libraries, and fill in the missing translations there. You just don't use SVN anymore, now you use the website! :)
This is a community effort. If you know there is a mistranslation and know the fix, fix it. Only thing babble manager/maintainer needs to do for you is add the key for new content.
I think the easiest way would be if Curse would make a MMOUI Minion plugin.
Minion is newer than CC and as such curse would be throwing away alot of dev time. The other issue with this is that CC seems to be a.) easier to use and b.) better at detecting the correct addon than minion is (YMMV, that's just my own experience with these clients).
I would love to see a Curse module for minion, with that said I do not think it could replace the CC for all users for the reasons stated above.
Unfortunately, no. I'm guessing that k,v is key and value, since those are the most used meanings, but as for a,b I'm still no closer to figuring what they mean. I've certainly become well versed in how the links are formatted, just every way I've thought of to adjust the code to account for their strings hasn't worked. *shrug, I'm usually pretty good at dissecting these things but I'll be danged if I just can't see this one.
a and b are also key and value but it's a nested call so they are called by different variable names
Are all addons started on the exact same frame? I was under the impression that they were loaded serially and as such should be darn near randomly spread out anyway.
To figure out where the problem lies you should do the following in the chat box:
/script TCatsUI:PLAYER_REGEN_DISABLED()
That should call the function and play the sound file directly. If the sound doesn't play then you know the error is in the PlaySoundFile call (not sure but might need escaped slashes in the path, or path is wrong, etc). If the sound plays fine then either the event registration isn't setting correctly (double check to make sure you are using the api correctly) or the event isn't firing when you think it should (make sure you are using the correct event for what you want to do).
Note: Chances are I or someone else could have told you exactly what to do to fix the issue, but "teach a man to fish" and you'll figure out these things much faster than posting and waiting for a reply.
No, a) is correct. The modifications they are making fairly well prove that they want to do something different than what LDB was designed for (albeit similar). The long and the short of it is simple... DO NOT MODIFY A LIBRARY THAT IS NOT YOUR OWN. If you want to take LDB to make some other lib that does what you want, fine, but modifying the library at run time proves fairly damn well that you don't get the way libs work in wow and what modifying the lib will do to other users of the lib... which proves why you SHOULDN'T be modifying the lib.
They are actually modifying the lib at runtime? O_O That's a nono.
I'll try to be as nice as possible in saying, that the way you are using the library shows :
a) You are using it for a purpose it was never designed for and in a way that totally goes against the "spirit" of its logic.
b) You don't care that you are breaking the upgrade path and/or the implication of callbacks for the addons embedding LDB.
c) You really don't understand how lua works.
d) All or some of the above.
For the love of all that's good and holy, please rethink your implementation (to say the least).
Remove the first part of a.) as it was specifically designed to be used an darn near any way that anyone wanted to create a spec for (even a non-published spec). Can't comment on the rest as I haven't looked at the code but we don't want to start spreading about the phrase "using it for a purpose it was never designed for" when talking about LDB.
And again I see Arrow being a complete arsehat about things.
0
Do you have "load out of date addons" checked on the character select screen?
0
This is a community effort. If you know there is a mistranslation and know the fix, fix it. Only thing babble manager/maintainer needs to do for you is add the key for new content.
0
Old != bad or broken. At least not necessarily.
0
0
Pretty sure he meant project comments. Threads for the most part seem not necessary with the new system.
0
Minion is newer than CC and as such curse would be throwing away alot of dev time. The other issue with this is that CC seems to be a.) easier to use and b.) better at detecting the correct addon than minion is (YMMV, that's just my own experience with these clients).
I would love to see a Curse module for minion, with that said I do not think it could replace the CC for all users for the reasons stated above.
0
a and b are also key and value but it's a nested call so they are called by different variable names
0
to the toc also or the LoadWith: line is ignored iirc
0
0
0
0
/script TCatsUI:PLAYER_REGEN_DISABLED()
That should call the function and play the sound file directly. If the sound doesn't play then you know the error is in the PlaySoundFile call (not sure but might need escaped slashes in the path, or path is wrong, etc). If the sound plays fine then either the event registration isn't setting correctly (double check to make sure you are using the api correctly) or the event isn't firing when you think it should (make sure you are using the correct event for what you want to do).
Note: Chances are I or someone else could have told you exactly what to do to fix the issue, but "teach a man to fish" and you'll figure out these things much faster than posting and waiting for a reply.
0
0
They are actually modifying the lib at runtime? O_O That's a nono.
0
Remove the first part of a.) as it was specifically designed to be used an darn near any way that anyone wanted to create a spec for (even a non-published spec). Can't comment on the rest as I haven't looked at the code but we don't want to start spreading about the phrase "using it for a purpose it was never designed for" when talking about LDB.
And again I see Arrow being a complete arsehat about things.