If, for some reason, you push a bunch of tags, the new packager will only package the latest 10 by date in the repository. Of course, just like the current packager, you could just turn off packaging before pushing and then turn it back on.
Unfortunately, that still confused the old packager.
Once you turn packaging back on, it would get into its usual scheme of building broken old packages all the time.
If you are trying to convert a SVN repository to Git, you would need to create a repository locally during the conversion process, and then push that repository onto the WoWAce repository.
There is no automatic conversion being performed by WoWAce. It'll switch the type and offer an empty Git repository - until you fill it.
Git repositories are initialized as "empty", so you cannot clone them right after creation - you need to create them locally and push them to the remote storage place.
Callbacks are always called with the widget as the first parameter, and the type of callback as the second.
So a proper signature for your callback function would be function(widget, event, key, checked), where widget == _BlacklistDropdown and event == "OnValueChanged". This would allow re-using the same function for multiple controls, but in your case you could just ignore the first parameters and call it a day.
Everytime your create a container, you should probably call SetLayout on it. The most common choice that mimicks AceConfig behavior would be "Flow". Other options would be "List" which just stacks widgets on top of each other, or "Fill", which is a special layout where one child fills the entire container (usually a container inside a container, ie. a scrollframe inside a frame)
There are a bunch of abilities with this behavior, its usually those modified by talent choices. There is one base talent ability per tier, and depending on which talent you chose in that tier, it "morphs" into another spell. For one thing that allows the talent choice to replace itself on your action bars magically, but it throws some stuff out of whack.
Garrision Ability uses the same system, as it morphs between different spells depending on your zone, but stays in the same action button of course.
0
Unfortunately, that still confused the old packager.
Once you turn packaging back on, it would get into its usual scheme of building broken old packages all the time.
0
There is no automatic conversion being performed by WoWAce. It'll switch the type and offer an empty Git repository - until you fill it.
Git repositories are initialized as "empty", so you cannot clone them right after creation - you need to create them locally and push them to the remote storage place.
0
0
Try logging in and go to http://www.wowace.com/themes/wowace/switch/, which should switch you to the default theme.
0
That should hopefully do it.
0
So a proper signature for your callback function would be function(widget, event, key, checked), where widget == _BlacklistDropdown and event == "OnValueChanged". This would allow re-using the same function for multiple controls, but in your case you could just ignore the first parameters and call it a day.
0
All your InlineGroups also don't.
0
0
There may be a potential fix for this issue in the latest alpha. Testing appreciated!
0
0
Never really bothered to try to fix it.. I should ask Shadowed if he still cares, and otherwise maybe try to fix it and just push the update.
0
0
Since you write those setter functions yourself, you know that values change, of course.
0
No. You should let your addon control the db, and if a user tries that hard to get around your addon and modify the db directly.. well their loss. :)
0
Garrision Ability uses the same system, as it morphs between different spells depending on your zone, but stays in the same action button of course.