For some reason Skinner seems to be lowering the alpha of the combat log text both on the combat log frame and on the worldmap frame. I've had to disable skinning of both frames in order to be able to read the text on them.
I checked the two text color settings in Skinner's color menu, and they're set to full opacity.
Yeah the Curse comments page is kind of useless for high-traffic addons because the layout deters structured/organized communication. Your best bet is probably to direct people to more desirable venues (ticket tracker and/or wowace forum) in big bold letters, and optionally disable Curse project page comments as further encouragement.
For some reason Skinner seems to be lowering the alpha of the combat log text both on the combat log frame and on the worldmap frame. I've had to disable skinning of both frames in order to be able to read the text on them.
I checked the two text color settings in Skinner's color menu, and they're set to full opacity.
I got bit by this last night for the first time in a while. It was most noticeable by MikScrollingBattleText not working, and less so by malfunctioning raid cooldown trackers, damage meters, and of course the raw combat log tab of my chat frame.
The issue persists through UI reload. I never logged out last night to try that method of "fixing" it. Is dropping to the character screen enough, or do you need to drop to the login screen?
I turned on Blizz floating combat text though and that seemed to work, so I guess it gets the data from a lower level or different source than the combat log does.
You'd think Blizz could code in some kind of combat log handshake test on login to make sure it's working and reset the system if it isn't.
I took a screenshot last night of Brann's yell at the end of the alliance version of the gunship battle. I forgot to screenshot Deathwhisper's death yell (doh).
Skinner is a necessary evil for me. It would be nice if there could be some kind of standard API for letting addon A tell addon B how to look. That still wouldn't obsolete Skinner thous because some authors don't care about look'n'feel configuration at all, so the only way for another addon to allow users to configure the look of the first one is by ugly hooking.
Edit: And Skinner's hooking of things has caused me to foolishly report bugs in addons that were broken by Skinner's hooking and that worked fine without Skinner running. I can understand why an author would want to be protected from erroneous bug reports from things like that.
Providing APIs where appropriate is a much better way to go because it means you can make more significant changes to your addon without having to worry about breaking compatibility with some other addon's fragile hooks into yours. I see addons break interoperability between each other all the time because of this, and while it's often unintentional (and usually gets fixed - eventually) it's still something that can be easily avoided by better coding methods (such as APIs).
BigWigs seems to track DeathWhisper by checking for her death event in the combat log, so I'm not sure why NRT wouldn't catch it. WoWWiki does list a death yell that could probably be used to track it in the enUS/enGB version if all else fails.
For the gunship battle, BigWigs doesn't seem to have a module (?) so I'm not sure what can be done there.
I'm going to check in the changes suggested by genetik, but I'm not going to push a release version nor bump the toc to 3.3 because of the issues mentioned by buterflykiss.
If someone can provide a list of itemIDs for 3.3 items that should be ignored, I can check in an update (not sure if I can push a release though, but at least there will be a new alpha).
Since tradeskills can now be linked, it doesn't make sense to have a query addon. Why spam instructions at people on how to get a link when you can just spam the link?
The API has always had horrible nomenclature. "Container" is specific to items in bags, but "inventory" seems to cover everything including the bags (and bank bags) themselves. "Equipment" would have been a much better name, but meh, it's years too late to fix it now.
Yeah that's pretty bad, especially for those of us who grew up playing text adventure games (or "interactive fiction" as the kids call it now) where it was common procedure to type "inventory" into the command parser to get a list of all the junk you're carrying around :p
0
0
Here's what I'm talking about:
Look at the text in the lower left corner of the worldmap frame.
0
0
Sure, if I can remember to. I haven't been playing WoW as much lately.
0
I checked the two text color settings in Skinner's color menu, and they're set to full opacity.
0
The issue persists through UI reload. I never logged out last night to try that method of "fixing" it. Is dropping to the character screen enough, or do you need to drop to the login screen?
I turned on Blizz floating combat text though and that seemed to work, so I guess it gets the data from a lower level or different source than the combat log does.
You'd think Blizz could code in some kind of combat log handshake test on login to make sure it's working and reset the system if it isn't.
0
0
Edit: And Skinner's hooking of things has caused me to foolishly report bugs in addons that were broken by Skinner's hooking and that worked fine without Skinner running. I can understand why an author would want to be protected from erroneous bug reports from things like that.
0
0
0
For the gunship battle, BigWigs doesn't seem to have a module (?) so I'm not sure what can be done there.
I'm going to check in the changes suggested by genetik, but I'm not going to push a release version nor bump the toc to 3.3 because of the issues mentioned by buterflykiss.
0
0
0
0
Yeah that's pretty bad, especially for those of us who grew up playing text adventure games (or "interactive fiction" as the kids call it now) where it was common procedure to type "inventory" into the command parser to get a list of all the junk you're carrying around :p