I'm not "pissed" about the changes but in my opinion it just doesn't work the way it is now. I do appreciate the work you put in it, and I'm looking forward to the new condensed sub forum look & feel. Furthermore I'll abide by the results of this poll whether I personally like it or not.
As for an actual poll comment: I think splitting out a category only when there's a certain amount of addons makes the most sense. That way there's never a subforum that feels empty, which I think is the main "problem" of the category setup.
Thanks for going through with this!
- Registered User
Member for 14 years, 4 months, and 24 days
Last active Fri, Oct, 4 2013 14:29:42
- 0 Followers
- 61 Total Posts
- 0 Thanks
Sep 10, 2006FWIW I hate this layout. Way too many things to click on to get any sense of 'what's happening' compared to the old way.Posted in: General AddOns
EDIT: realized this was not a constructive comment -- I'm with Tekkub, use the wiki to categorize things and point to the right forum threads in there.
Sep 7, 2006In addition to what the others said, if you see the full error message, there's a clue to what addon is causing errors in the other lines. I can't find a good example right now, but usually it's like this:Posted in: General AddOns
[2006/09/07 11:22:33-31]: Tablet-2.0\Tablet-2.0.lua: I got passed a stupid argument
Dewdrop-2.0\Dewdrop-2.0.lua:456: in function PassArgsToTablet
StupidAddon\StupidAddon.lua:123: in function ImStupid
You can see that StupidAddon is at fault by looking at the bottom line.
That said, I'll doublecheck the stripping of Interface\Addons, to see that it doesn't strip out useful parts.
Sep 1, 2006Yes, that's the throttling in action. It means that the error listed before that message has occured another time in the past 30 seconds. Most of the time it's an addon that bugs either in a timer, or else throws an error upon use of an ability that you use multiple times per minute.Posted in: General AddOns
Aug 30, 2006OK, I implemented error throttling in the latest version. After a maximum of 30 seconds it'll give you a count of repeats of the last error. That means that if you have an addon that bugs every second, you'll still get an error every 30 seconds, but that's a lot more manageable than it was before :)Posted in: General AddOns
Furthermore BugSack doesn't by default output anything to the chatframe anymore, it's a new toggle that you can find in the menu.
Hopefully this is enough for most people's needs!
Aug 14, 2006OK, I just found the cause of the crashes -- it seems WoW has an internal limit on the size of strings in the SavedVariables\*.lua files, and one of your bug messages was longer than that. I've put in a guard against such long messages in !BugGrabber, but you will have to delete your old SavedVariables\!BugGrabber.lua if you're currently suffering this bug (it doesn't make sense to put in scanning / fixing code for this edgecase so that everyone's load times will suffer from BugGrabber's over zealous fixing of messages that in 99.9% of the cases are fine anyway).Posted in: General AddOns
So, be sure to update to the latest SVN to prevent this from happening in the future. Thanks again for the nice report, Devla! And definitely no cookie for Blizzard for not having a guard against this kind of thing in their saving/loading code.
Oh and thomasmo, I added your zhCN translation to the repository, please check if I did that correctly because I have no way of testing it :)
Aug 14, 2006thomasmo: thanks for the translation, I'll check it into the SVN as soon as possible!Posted in: General AddOns
Devla: Many thanks for the report! I can now finally reproduce the crash on reload. I do not however see something very wrong in !BugGrabber, but at least now I can try to narrow it down to something in that file. However because of it's unobviousness, I can't give an ETA to the fix yet :-/ I'll try to fix it as soon as possible however.
Sent: I doubt that it's my plugin doing that, are you still seeing this after updating FuBar?
teedog: I don't know about supressing duplicate errors, because sometimes it is very relevant to a developer to know how many times a certain error occurred (IE for every person in a raid, or just for the pets?). Still, I'm debating adding a 'totally silent' mode that won't spam the chat frame nor make a sound. Now that the FuBar plugin shows the nr of errors I guess it's not as necessary anymore to output to the chat frame anyway. Will that do?
Aug 11, 2006OK, I think I fixed that last reported error locally but unfortunately I'm unable to test ingame until tomorrow at the earliest, so please bear with me until then (a lot of planned RL events this weekend).Posted in: General AddOns
scae: I agree with Kyahx here, for normal playing you don't need the full chat frame output, just a simple message.
Phanx: I hope the silence means that you haven't seen a freeze anymore?
My short TODO-list right now:
- check the fix for the BugSackFu error
- fix the frame scale, it's way too big at UI scale 0.64 right now
- check whether BugSackFu really runs without FuBar (it should attach to the minimap)
Anything else to be done? Suggestions? (note that I can't promise when I'll do stuff :-) )
Aug 10, 2006That's good news! I know why that error is happening, I can probably fix it tonight. I just learned that FuBar-2.0 plugins don't even have to depend on FuBar so I needed to rewrite a bit of it in any case.Posted in: General AddOns
Aug 9, 2006I've put up a new version on the SVN that includes more loadtime checks, which should guard against load time errors in !BugGrabber itself. Unfortunately I haven't yet been able to reproduce the reported crashes so I'm still unclear as to what's causing it. Please keep sending me your SavedVariables\!BugGrabber.lua / SavedVariables\BugSack.lua files if you encounter these kinds of problems. It might also be worth checking out whether enabling only !BugGrabber and disabling BugSack fixes your problem.Posted in: General AddOns
I've also done the following in this version:
- tweaked the reporting of load time errors so that BugSack will catch all load time errors if it's enabled
- improved the frame somewhat by making it a bit bigger, making sure it only shows one error at a time and adding first/last/next/prev buttons to go through the list of errors
- the FuBar plugin now shows only the first line of errors in it's tooltip, and the tooltip is detachable and clickable to show specific errors
Phanx: ok, that's clear. Unfortunately I'm totally unable to reproduce it (of course). But check out the latest version, I've put some more checks in that might fix things (I hope). If you do find a way to reproduce it, let me know.
LordRhys: there's a small buglet in FuBar-2.0 right now with the 'development tools' category, but it shows up for me in the 'Others' category. Please make sure you run the latest FuBar2 along with all the latest external libraries.
All comments appreciated as always.
Aug 9, 2006Lewzephyr: someone else reported the same problem also. Can you send me your SavedVariables\!BugGrabber.lua and SavedVariables\BugSack.lua by PM (or attach them here) ? I've got one set that makes WoW crash but it won't hurt to have more. Furthermore if you delete those I think the problem will go away.Posted in: General AddOns
Phanx: that's also a serious problem. What other addons do you have installed? What are the last errors as shown by BugSack? You mention that it also happens without SavedVariables, but without any errors having been reported?
I will test today to see whether I can fix the crash on login.
- To post a comment, please login or register a new account.