WoW:API message: Difference between revisions
Jump to navigation
Jump to search
({{framexmlfunc|FrameXML/BasicControls.xml}} __NOTOC__) |
m (Move page script moved page API message to API message without leaving a redirect) |
||
(6 intermediate revisions by 6 users not shown) | |||
Line 1: | Line 1: | ||
{{framexmlfunc|FrameXML/BasicControls.xml}} | {{framexmlfunc|FrameXML/BasicControls.xml}} | ||
Displays a message box. | Displays a message box. | ||
message("text") | |||
== Arguments == | |||
;text : String - message to be displayed. | |||
==Details== | ==Details== | ||
* Pops up a message box displaying the argument with an "Okay" button inside a frame. | |||
* 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}}(...); | |||
Latest revision as of 04:46, 15 August 2023
- This function is implemented in Lua here FrameXML/BasicControls.xml.
Displays a message box.
message("text")
Arguments[edit]
- text
- String - message to be displayed.
Details[edit]
- Pops up a message box displaying the argument with an "Okay" button inside a frame.
- 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(...);