Now on the SVN in /trunk: a rewritten !BugGrabber / BugSack.
Changes that I made:
- BugSack now unconditionally depends on !BugGrabber. This is because I changed !BugGrabber to grab the bugs; BugSack is now only a shell that displays the errors. I did this because errors in Ace2 libraries tended to keel over other Ace2 addons. Since BugSack is now an Ace2 addon, that meant errors got lost. The new BugGrabber should print errors to the chat frame if BugSack is dead, which prevents errors from getting lost alltogether.
- Added a new FuBar-2.0 plugin that'll show the current nr of errors.
Changes kergoth made:
- Added a backtrace to errors; now you can see the whole call stack
- Prettified the error message a little (no more Interface\ clutter)
small bug i'm having is it not remembering when i disable the sound. it might be because the !BugGrabber saved variables is not being written to disk for some reason. Bugsack saved variables is being written just fine.
It's been renamed to BugGrabber because it seems that lots of computers don't load addons in alphabetical order anyway, so the '!' thingy was only annoying. Although I'm considering reverting that change because it didn't hurt anyone either, and it helped at least one class of people.
In any case, I'm told the only way to make sure it's loaded early is to add a '## LoadWith: SomeEarlyAddon' line to the .toc where you need to determine 'SomeEarlyAddon' yourself unfortunately.
I'd love to have 'LoadWith: FrameXML' working; if someone can make a post to that effect on the US WoW UI forums stating that it might help in this case, maybe slouken will consider it.
The whole point of !BugGrabber was, that some Bugs are happening before BugSack got loaded... Rowne etc came to the conclussion that Windows-Machines load Addons in alphabetical order (whereas Linux/Wine and maybe Mac are loading them in order of creation or last changed or something).
If you now, rename !BugGrabber to BugGrabber, you can just remove it I think because it's of no purpose when it's not loaded first.
would that help? As I'm using a Mac, the ! never worked for me anyway.
Most non-developers don't need to track bugs that occur right on login (there shouldnt be any), but want to make sure no addon pops up an error message in the middle of a raid boss fight. So they don't need the "!". And as for developers: well, they can always add the addons they want to track on login to LoadWith. I guess they'd manage to edit a .toc file easily. :)