WoW:API message: Difference between revisions

WoW:API message (source)

279 bytes removed , 15 August 2023

m

Move page script moved page API message to WoW:API message without leaving a redirect

Anonymous user

@@ Line 1: / Line 1: @@
-<br>{{framexmlfunc|FrameXML/BasicControls.xml}} __NOTOC__
+{{framexmlfunc|FrameXML/BasicControls.xml}}
- message("text");
 Displays a message box.
+ message("text")
+== Arguments ==
-== Parameters ==
+;text : String - message to be displayed.
-=== 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.
+* 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 1.10, message("text") no longer seems to work inside instances under certain conditions.  The fix for this is currently unknown.
+* As of 3.2 message() is broken / Depreciated as the message frame is no longer defined. Suitable alternative is {{api|print}}(...);
-: As of 2.1, the cvar "scriptErrors" must be set to 1 for this to work.  This can be accomplished through a call to [[API SetCVar |SetCVar]]().
-: 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.