Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Page
Talk
English
Views
Read
Edit
History
More
Search
Navigation
Home
Random page
Help using wiki
Editions
for WoW
for WildStar
for Solar2D
Documentation
for WoW
for WildStar
Reference
WoW
⦁ FrameXML
⦁ AddOns
⦁ API
⦁ WoW Lua
WildStar
⦁ AddOns
⦁ API
⦁ WildStar Lua
Engine
Tools
What links here
Related changes
Special pages
Page information
Site
Recent Changes
Editing
AddOn Studio for World of Warcraft history
(section)
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== 20513.0 (5/13/2012) == Lua Editor: * Fix for rare editor freezing on incomplete Lua return statement. * Fix for IntelliSense word completion error, on enter key if already matching but not selected. * Fix for regression where function completion tooltips not showing. * Performance and stability improvements in Lua parser. FrameXML: * Fix for ToolBox not working on Windows XP after AddOn Studio update * Fix for crashing on unregistered WoW install Project: * Updated repository support * Minor fixes for project load and unload General: * New AddOn Studio option for custom WoW install location * Tutorial file size cleanup * General performance improvements Notes: * The new custom WoW install location option is important for those with both Trial and Retail installs as the content *is* different, or for testing Preview and Current versions, etc... The old behavior was for AddOn Studio to use the wow registry entry to automatically locate and use wow for content, with no way to disable or change this behavior. The Custom Deploy Location setting still allows to deployment to a different base install location, even if the new wow location option is set. The Custom ToolKit Location option still allows the addition of a blizzard toolkit content location, searched before the base wow location. The custom deploy location is no longer a part of the compound search path, as the base wow install path can be changed, and could otherwise make for a confusing and fickle content set when editing for some workflows. These more flexible options also allow for the possibility of deploying to another machine running wow for testing without the cost of pulling content for editing over the wire, or conversely using a shared networked toolkit and base install with a local deploy for functional testing, or testing/content location to/from another platform like OSX or other VMs, and so on... * Version 20513 is the first version to fully support complex, large scale, professional level, multi system, multi platform, and multi user workflows, with remote, group, and IDE automation support, via file system and / or source control system.
Summary:
Please note that all contributions to AddOn Studio are considered to be released under the Creative Commons Attribution-NonCommercial-ShareAlike (see
AddOn Studio Wiki:Copyrights
for details).
Submissions must be written by you, or copied from a public domain or similar free resource (see
AddOn Studio Wiki:Copyrights
for details).
Cancel
Editing help
(opens in new window)