Authors CurseForge

Quote from LaoTseu

Note that deleting the tags on my clone and doing a git push doesn't remove the tags on the WoWAce repositories.

You can push the removal of tags.

Quote from stassart

Wowace is the older site and is missing some features like being able to manually upload files instead of going through the packager.

Actually thats intentional, and not a missing feature. CurseForge and WoWAce are practically the same website (different skin, mind you), just that WoWAce enforces using the packager.

Zeldo tells me that Grid should be fixed now, if you want to use the default packager again.

Might want to check the project settings on CurseForge either way, I do not know if he turned packaging on for testing purposes when deploying the fix.

Quote from Galvin

Packager stuck again. Hope this can get fixed. Tagged a beta around 12 hours ago.
svn://galvin@svn.curseforge.net/wow/galvins-unitbars/mainline/tags/5.25 beta

Your beta has been built now.

The Icon widget fires an OnClick callback like a button, so you can run any code in that callback. How to open the window I don't know off-hand.

Passing Texture FileIDs to the AceGUI Icon SetImage function should be working fine, as far as I can tell.

Its been the weekend, but I've been told that the issue currently affecting Grid is quite fundamental in the packager, so they are having trouble deploying a quick fix.

I'll try to inquire again tomorrow when they are back at work.

Phanx apparently turned packaging back on, I've disabled it again in the meantime, there is no sense in spamming the project with old zips every couple minutes.

Sounds like you just have UI issues. Just store it internally with Spell IDs and translate to spell names in the local language whenever its shown to a user, or send to the game.

In code, you can always use comments to explain what the IDs are.

A spell database is just a bad idea, and Babble-Spell will not be coming back. It has always been notoriously out of date, both in spell availability in general and the localizations of those spells.

You may want to rethink your approach, translating spell names from English to localized is not something that's generally a good idea.

It's best to deal with IDs or fully localized strings if you must, but translating between languages is bad.

Zeldo wanted to get the underlying bug fixed because it affects more then one addon. I'll poke him again on an update.

I haven't heard back from the Curse guys yet, I'll inquire when they wake up if they did deploy a fix.

Its being worked on right now. If you could refrain from pushing more tags in the meantime, that would be super. :)

You wouldn't dare to subject us to anything but release quality addons, would you Seerah? Would you?!?!

Are you sure you pushed the tag? I didn't see it in the repository.

You have a new file.