Got this error today after many hours of errorfree play:

Message: Interface\AddOns\NeonChat\NeonChat.lua:25: Usage: <unnamed>:SetBackdrop(nil or {bgFile = "bgFile", edgeFile = "edgeFile", tile = false, tileSize = 0, edgeSize = 32, insets = { left = 0, right = 0, top = 0, bottom = 0 }})
Time: Thu Nov 5 23:18:34 2009
Count: 1
Stack: [string "Interface\FrameXML\BasicControls.xml:<Scrip..."]:18: in function <[string "Interface\FrameXML\BasicControls.xml:<Scrip..."]:4>
[C]: ?
[C]: in function `SetBackdrop'
Interface\AddOns\NeonChat\NeonChat.lua:25: in main chunk

Locals: (*temporary) = <unnamed> {
0 = <userdata>
}

is there a way to keep the "chat" highlighted always with the last channel color used? and the edit box highlighted only when you type?

as it stands now, the whole border isnt highlighted untill i type, id like it alwys showing.

I like having my editbox highlight, but is there a way to not have the frame highlight as well? Thanks.

I know Chatter can do this, but not for the entire chat box so I'll try this out, thanks

__________________
KittyUI | My Home on the Web

This would of course only be the case if it was true that every person who downloaded the add-on had to enable load out of date.

If all 22,000 people (based on number of downloads) downloaded this mod and had to do this it really takes all the end users 220000 seconds or 3667 minutes or 60 hours... 10 seconds is really several orders of magnitude when you have such a large user base.

Care to reread what I wrote, but with a bit more care? You both seem to have made the assumption that I was referring to bumping .toc numbers, although I never even made a mention about .toc numbers! Guess I should have made more of an effort to make my comment clear, precise and more to the point. If the end-user wants the .toc to reflect the correct game version then they can edit that themselves, takes all of 10 seconds!

However, my point was actually about making it clear whether an addon is compatible, and therefore working, with a specific game version. By making use of whatever resources a site provides to indicate that will make it easier for end-users to see at a glance what is working and what might not be working! I think this would be of much more benefit around patch days, but what the heck, I was simply trying to express my thoughts on this but it would appear that my comments were misunderstood.

__________________

And? WoWI has a nice bit of text that can specifically indicate a mod works with a version without a TOC bump, Curse as well can let you specify what version a file works with without requiring authors to push versions for a single line change.

Pushing an addon purely for a toc bump is silly and adds extra load onto resource sites because people are redownloading the addon for a single number change. It's even worse on patch days when the sites are generally bogged down already without people making it worse with worthless updates.

Their loss? If it's not in the outdated category and users aren't ranting and raving in the comments that it's broken, then it most likely works just fine.

And "works with vX.X" has nothing to do with the TOC number, authors could edit their page and check that yet never update the TOC version in their file. Simply put, TOC number is *MEANINGLESS* Why should all that bandwidth be wasted to change a single char so that you *think* the addon has been updated? That's stupid.

__________________
I have reached enlightment.
Thank you bacon!

Unfortuantely some people simply won't even look at addons that aren't listed as "Works with vX.X"! If people can see at a glance that an addon is compatible then they'll be more likely to take the time to check out the details and maybe give it a try, but if they think it's not compatible they'll just pass on by without a second look!

__________________

Your addon saved me from what would have been a rather awkward mt within the first ten minutes of install. Thanks!

Thank you for updating, love this mod. its a stroke of brilliance