WoW:API message: Difference between revisions
Jump to navigation
Jump to search
(update message's new behavior) |
No edit summary |
||
| Line 29: | Line 29: | ||
: As of 3.1, message() is no longer an alias of the [[API ERRORMESSAGE|_ERRORMESSAGE]] function. It is a standalone function that bypasses the cvar "scriptErrors" entirely and always displays an error box. | : As of 3.1, message() is no longer an alias of the [[API ERRORMESSAGE|_ERRORMESSAGE]] function. It is a standalone function that bypasses the cvar "scriptErrors" entirely and always displays an error box. | ||
: As of 3.2 message() is broken / Depreciated as the message frame is no longer defined. Suitable Alternative is [[API print |print]] | |||
Revision as of 03:39, 7 August 2009
This function is implemented in Lua here FrameXML/BasicControls.xml.
message("text");
Displays a message box.
Parameters
Arguments
- ("text")
- text
- String - message to be displayed.
Returns
- nil
Example
message("This is an example.");
Details
- Pops up a message box displaying the argument with an "Okay" button inside a frame.
- (?) As of 1.10, message("text") no longer seems to work inside instances under certain conditions. The fix for this is currently unknown.
- As of 2.1, the cvar "scriptErrors" must be set to 1 for this to work. This can be accomplished through a call to SetCVar().
- As of 3.1, message() is no longer an alias of the _ERRORMESSAGE function. It is a standalone function that bypasses the cvar "scriptErrors" entirely and always displays an error box.
- As of 3.2 message() is broken / Depreciated as the message frame is no longer defined. Suitable Alternative is print