WoW:API and scripting quirks - Revision history

Move page script: Move page script moved page API and scripting quirks to WoW:API and scripting quirks without leaving a redirect

2023-08-15T04:45:03Z

Move page script moved page API and scripting quirks to API and scripting quirks without leaving a redirect

← Older revision	Revision as of 04:45, 15 August 2023
(No difference)

WoWWiki>Starlightblunder: remove deleted faq link

2009-04-07T00:06:13Z

remove deleted faq link

← Older revision		Revision as of 00:06, 7 April 2009
Line 1:		Line 1:
			{{cleanup\|Mostly out of date and misguided; merge into relevant articles and delete}}

	== World of Warcraft Scripting Quirks ==		== World of Warcraft Scripting Quirks ==
	* [[Macros]]		* [[Macros]]
Line 34:		Line 36:
	** If you declare a local variable inside an code block (such as an IF block), it is only available inside that code block.		** If you declare a local variable inside an code block (such as an IF block), it is only available inside that code block.
	** See [[Lua Scope]] for a complete description of the implications of Lua's variable scoping.		** See [[Lua Scope]] for a complete description of the implications of Lua's variable scoping.

	~~== See also ==~~
	* [[Interface Customization FAQ]]

	[[Category:Interface customization]]		[[Category:Interface customization]]

WoWWiki>KirkBot: Typo fixing using AWB

2008-08-07T21:16:16Z

Typo fixing using AWB

← Older revision		Revision as of 21:16, 7 August 2008
Line 13:		Line 13:
	** OnUpdate handlers are only called when the frame is visible.		** OnUpdate handlers are only called when the frame is visible.
	** OnUpdate handles are called ''every'' frame. Use with care.		** OnUpdate handles are called ''every'' frame. Use with care.
	** When nesting frames, you can access the parent frame name in XML names ~~with~~ with $parent, this is a textual substitution and cannot be used in Lua. The Lua equivalent to $parent is the GetParent() method of the frame (e.g. getglobal(Frame:GetParent():GetName().."Button") is the same as $parentButton).		** When nesting frames, you can access the parent frame name in XML names with $parent, this is a textual substitution and cannot be used in Lua. The Lua equivalent to $parent is the GetParent() method of the frame (e.g. getglobal(Frame:GetParent():GetName().."Button") is the same as $parentButton).
	** All [[Frames]] have a GetID() function which will obtain the ID specified in the XML. ID's must be positive integers enclosed in quotes: ie. id="1" or id="20"		** All [[Frames]] have a GetID() function which will obtain the ID specified in the XML. ID's must be positive integers enclosed in quotes: ie. id="1" or id="20"
	** If you don't specify parent="UIParent" in your top-level frames, your frames won't be scaled according to the currently active UI scale. This can lead to some hair-pulling as you try to figure out why your fonts are so huge. (But, in some cases, not having that scaling might be desirable.)		** If you don't specify parent="UIParent" in your top-level frames, your frames won't be scaled according to the currently active UI scale. This can lead to some hair-pulling as you try to figure out why your fonts are so huge. (But, in some cases, not having that scaling might be desirable.)
Line 35:		Line 35:
	** See [[Lua Scope]] for a complete description of the implications of Lua's variable scoping.		** See [[Lua Scope]] for a complete description of the implications of Lua's variable scoping.

	== ~~Also~~ See ==		== See also ==

	* [[Interface Customization FAQ]]		* [[Interface Customization FAQ]]


	~~<br>~~
	~~<br>~~
	[[Category:Interface customization]]		[[Category:Interface customization]]

WoWWiki>Charibot: catfix

2008-07-07T18:33:24Z

catfix

← Older revision		Revision as of 18:33, 7 July 2008
Line 42:		Line 42:
	<br>		<br>
	<br>		<br>
	[[Category:Interface ~~Customization~~]]		[[Category:Interface customization]]

WoWWiki>Pcj at 18:26, 28 August 2007

2007-08-28T18:26:10Z

← Older revision		Revision as of 18:26, 28 August 2007
Line 1:		Line 1:
	== World of Warcraft Scripting Quirks~ ==		== World of Warcraft Scripting Quirks ==
	* [[Macros]]		* [[Macros]]
	** Can only cast spells from a hotkey or mouse click		** Can only cast spells from a hotkey or mouse click
Line 35:		Line 35:
	** See [[Lua Scope]] for a complete description of the implications of Lua's variable scoping.		** See [[Lua Scope]] for a complete description of the implications of Lua's variable scoping.

	== Also See~ ==		== Also See ==

	* [[Interface Customization FAQ]]		* [[Interface Customization FAQ]]

WoWWiki>Zobes90: /* Also See */

2007-08-28T17:16:19Z

Also See

← Older revision		Revision as of 17:16, 28 August 2007
Line 1:		Line 1:
	== World of Warcraft Scripting Quirks ==		== World of Warcraft Scripting Quirks~ ==
	* [[Macros]]		* [[Macros]]
	** Can only cast spells from a hotkey or mouse click		** Can only cast spells from a hotkey or mouse click
Line 35:		Line 35:
	** See [[Lua Scope]] for a complete description of the implications of Lua's variable scoping.		** See [[Lua Scope]] for a complete description of the implications of Lua's variable scoping.

	== Also See ==		== Also See~ ==

	* [[Interface Customization FAQ]]		* [[Interface Customization FAQ]]

WoWWiki>Starlightblunder: /* World of Warcraft Scripting Quirks */ strike CVar immediate output, not true as of 2.1.0 (or earlier)

2007-06-01T22:44:52Z

World of Warcraft Scripting Quirks: strike CVar immediate output, not true as of 2.1.0 (or earlier)

← Older revision		Revision as of 22:44, 1 June 2007
Line 20:		Line 20:
	* Output to the outside world		* Output to the outside world
	** The only file output allowed is when the UI engine saves variables before it exits or reloads. Addons use the "<tt>## [[SavedVariables]]:</tt>" header to indicate which data they wish to save.		** The only file output allowed is when the UI engine saves variables before it exits or reloads. Addons use the "<tt>## [[SavedVariables]]:</tt>" header to indicate which data they wish to save.
	** Another way to output data is to save certain variables using the SetCVar() function. This will immediatly do an export of the config.wtf file that contains various in game variables. This will not allow you to create new variables to export out, just set non default values to certain in game variables.

	* [[World of Warcraft API\|Functions]]		* [[World of Warcraft API\|Functions]]

WoWWiki>Rowaasr13: LUA -> Lua, it is word, not abbreviation. Get rid of "code". Remove unnecessary _ in article title.

2007-03-29T09:12:00Z

LUA -> Lua, it is word, not abbreviation. Get rid of "code". Remove unnecessary _ in article title.

← Older revision		Revision as of 09:12, 29 March 2007
Line 13:		Line 13:
	** OnUpdate handlers are only called when the frame is visible.		** OnUpdate handlers are only called when the frame is visible.
	** OnUpdate handles are called ''every'' frame. Use with care.		** OnUpdate handles are called ''every'' frame. Use with care.
	** When nesting frames, you can access the parent frame name in XML names with with $parent, this is a textual substitution and cannot be used in ~~LUA code~~. The ~~LUA~~ equivalent to $parent is the GetParent() method of the frame (e.g. getglobal(Frame:GetParent():GetName().."Button") is the same as $parentButton).		** When nesting frames, you can access the parent frame name in XML names with with $parent, this is a textual substitution and cannot be used in Lua. The Lua equivalent to $parent is the GetParent() method of the frame (e.g. getglobal(Frame:GetParent():GetName().."Button") is the same as $parentButton).
	** All [[Frames]] have a GetID() function which will obtain the ID specified in the XML. ID's must be positive integers enclosed in quotes: ie. id="1" or id="20"		** All [[Frames]] have a GetID() function which will obtain the ID specified in the XML. ID's must be positive integers enclosed in quotes: ie. id="1" or id="20"
	** If you don't specify parent="UIParent" in your top-level frames, your frames won't be scaled according to the currently active UI scale. This can lead to some hair-pulling as you try to figure out why your fonts are so huge. (But, in some cases, not having that scaling might be desirable.)		** If you don't specify parent="UIParent" in your top-level frames, your frames won't be scaled according to the currently active UI scale. This can lead to some hair-pulling as you try to figure out why your fonts are so huge. (But, in some cases, not having that scaling might be desirable.)
Line 33:		Line 33:

	* Variables		* Variables
	** If you declare a local variable inside an code (such as an IF block) ~~block~~, it is only available inside that code block.		** If you declare a local variable inside an code block (such as an IF block), it is only available inside that code block.
	** See [[~~Lua_Scope~~]] for a complete description of the implications of Lua's variable scoping.		** See [[Lua Scope]] for a complete description of the implications of Lua's variable scoping.

	== Also See ==		== Also See ==

WoWWiki>WoWWiki-Shirik at 08:57, 29 March 2007

2007-03-29T08:57:15Z

@@ Line 32: / Line 32: @@
 **** "|c" doesn't have the same problem, but will cause the text after it not to show.
-* Variables (not really a "quirk", more like a "need to know").
+* Variables
-** If you declare a local variable inside an IF block, it is only available inside that IF block.
+** If you declare a local variable inside an code (such as an IF block) block, it is only available inside that code block.
-*** In Example 1, "Something" will never print. While in Example 2, "Something" does print.
+** See [[Lua_Scope]] for a complete description of the implications of Lua's variable scoping.
 == Also See ==

WoWWiki>Egingell: Changed my "quirk"

2007-03-29T08:36:54Z

Changed my "quirk"

← Older revision		Revision as of 08:36, 29 March 2007
Line 32:		Line 32:
	**** "\|c" doesn't have the same problem, but will cause the text after it not to show.		**** "\|c" doesn't have the same problem, but will cause the text after it not to show.

	* Variables		* Variables (not really a "quirk", more like a "need to know").
	** If you declare a variable inside an IF block, ~~any attempt to compare the value will fail~~.		** If you declare a local variable inside an IF block, it is only available inside that IF block.
	*** In Example 1, "Something" will never print. While in Example 2, "Something" does print.		*** In Example 1, "Something" will never print. While in Example 2, "Something" does print.
	*** See [[Talk:API_and_scripting_quirks#Variables\|Talk]] for more details.		*** See [[Talk:API_and_scripting_quirks#Variables\|Talk]] for more details.
Line 41:		Line 41:
	local someOtherVar = true; -- someOtherVar declared inside an IF block.		local someOtherVar = true; -- someOtherVar declared inside an IF block.
	end		end
	Print(tostring(someOtherVar));		Print(tostring(someOtherVar)); -- Prints "nil" because the variable does not exist.
	if someOtherVar then		if someOtherVar then
	Print("Something"); -- This never gets executed.		Print("Something"); -- This never gets executed.
Line 48:		Line 48:
	-- Example 2		-- Example 2
	local someVar = true;		local someVar = true;
	local someOtherVar; -- someOtherVar declared before an IF block.		local someOtherVar; -- someOtherVar declared before (outside) an IF block.
	if someVar then		if someVar then
	someOtherVar = true;		someOtherVar = true;