Hello everyone. If you're a user of my addons, it's probably no secret I haven't been active lately. I've essentially stopped playing WoW since a few months and for the first time, I don't think I'll be returning. My account is still active for the occasional emergency fix, but I feel that I need to find people to help maintain addons that actually play the game.
Some of the most popular addons I maintain are:
Magic Runes (original author)
Bulk Mail Inbox and Bulk Mail (maintainer, Ace3 port)
MagicMarker (original author)
Button Bin (original author)
Instead of listing all my addons, you can view them all from here:
If you're interested in taking over maintenance and development of one or more of my addons, send me a PM. Details such as curse points allocation will be discussed on a case by case basis and will vary based on what you end up doing.
I did the other day but didn't get further that day than checking it out and playing around a bit. I'm a big Intellij user (at work) and it's definitely something I've been missing.
So that's nice but I'd still want to have a compile that happens and shows all errors for all files in the project. Finding a red line isn't exactly easy if it's not right where I am at the moment.
Here's an idea for an improvement - make it possible to compile the project (essentially running luac -p on the files) without running. right now there doesn't seem to be a way to actually verify that a file is correct syntax without reloading in WoW or manually making an ant script that runs luac.
Indeed. It's something else. I'm using it for BulkMail and BulkMail Inbox as well as the MagicMarker LDB plugin (finally replaced that FuBar thing). They are naturally not used as exclusive configuration paths but for very simple config stuff, it's a lot quicker to just toggle an option in a menu, especially since it's unfortunately unreliable to open the module configuration if you use the Blizzard Interface:Addons methods (if you have a lot of addons).
Again this is hardly meant to replace the dialog, or blizzard options but as a convenient option for simple configuration.
BuffEnough is maintained again, just as a FYI. I'm not sure what the resource usage is (never tested, but never noticed an issue). That said, the goal of BE is to not require much configuration - it should figure things out itself. I think it's in a pretty good shape now.
The default rune bar currently shows up after every loading screen despite it being disabled in magic runes' settings. I can go back into magic runes' settings after this happens and toggle it back off. The default rune bars will then stay off until exiting any loading screen again.
I believe this should be fixed as of the last release. I added another trigger to turn them off (also when exiting vehicles).
I don't know if you have any new features planned for this mod involving cataclysm, but I'd like to suggest adding an effect to make it obvious when runic empowerment generates a new fully depleted rune and show clearly what rune it generated. I would suggest something like make that rune highlight, flash, or display a border around it.
Hmm. This might indeed be a nice feature. I'll see if I can add this in.
Specifically sold on AH? I've tested by sending cash to me and that worked fine.
Edit: I think I found the root cause for this. It did cause display issues at least. I just tried to "take cash" with some 7 AH sold emails and it worked fine. Likely related to the same issue that broke filtering of mails.
It's used in BulkMail2 primarily for the purpose of configuring auto-send rules (the most deep structure being PT31 sets), not options. I personally liked the original dewdrop-based interface in BM2 so I saw no reason to change it. It wasn't necessarily the quickest path either.
It's meant to replace dewdrop yes. I wouldn't use it for very deep menus in general, but it definitely has its uses. Code has been reformatted to what I normally use but I don't take responsibility for most of the code since I didn't write it. :-)
Did fix some Ace3 compatibility issues with the 'info' structure (I hope) and fixed some issues with sliders and groups that get data from a method.
Is this perfect and awesome? No. Did it help me convert BulkMail2 away from ace2 libraries faster - definitely.
Antiarc did most of the details. I just fixed the remaining bugs to make it work for my use cases. If you find bugs feel free to create tickets for them of course. Remember, this project was dormant for years in a totally non-working state. :)
Anyway, I added some images to the project page and the first post. The border/color will use the theme of the tooltips as set by the user (similar to what LibQTip does).
0
0
Some of the most popular addons I maintain are:
Magic Runes (original author)
Bulk Mail Inbox and Bulk Mail (maintainer, Ace3 port)
MagicMarker (original author)
Button Bin (original author)
Instead of listing all my addons, you can view them all from here:
http://www.wowace.com/profiles/dhedbor/
If you're interested in taking over maintenance and development of one or more of my addons, send me a PM. Details such as curse points allocation will be discussed on a case by case basis and will vary based on what you end up doing.
0
0
0
0
Again this is hardly meant to replace the dialog, or blizzard options but as a convenient option for simple configuration.
0
0
I believe this should be fixed as of the last release. I added another trigger to turn them off (also when exiting vehicles).
0
Hmm. This might indeed be a nice feature. I'll see if I can add this in.
0
Edit: I think I found the root cause for this. It did cause display issues at least. I just tried to "take cash" with some 7 AH sold emails and it worked fine. Likely related to the same issue that broke filtering of mails.
0
0
0
Did fix some Ace3 compatibility issues with the 'info' structure (I hope) and fixed some issues with sliders and groups that get data from a method.
Is this perfect and awesome? No. Did it help me convert BulkMail2 away from ace2 libraries faster - definitely.
0
Anyway, I added some images to the project page and the first post. The border/color will use the theme of the tooltips as set by the user (similar to what LibQTip does).
0