Editing WoW:API CreateFrame (section)

== Notes ==
* CreateFrame() was added in 1.10
* The fourth argument, inheritFrame, was added in 1.11
* Frames CANNOT be deleted. Reuse them.
* The frame's [[UIHANDLER_OnLoad|OnLoad handler]], which will only exist if inherited, will be executed during the CreateFrame call. Any OnLoad script handlers set after CreateFrame() will not execute; consider adding any non-inherited OnLoad code directly after a CreateFrame call or use XML frames instead.
* The returned frame reference is not strictly necessary because you can access frames by their global name if you give them one. For performance reasons, however, it is advised to store frame references in local variables and use those instead of getting frames by their global name.
* See also [[API_Frame_SetScript]] to handle OnFunction scripts when not using a template.
* The most common uses for this function are:
** Creating anonymous [[Events (API)|event handlers]].
** Creating anonymous [[Widget handlers|script handlers]].
** Creating frames on the fly for occasions when you don't know how many frames will be needed.
** Creating infrequently used frames "on demand", for example: config dialogs, raid frames.
* Never forget to unset the frames parent, if you want to get rid of a frame. I would suggest to hide the frame via frame:[[API_Region_Hide|Hide]]() and to use frame:[[API_Region_SetParent|SetParent]](nil) afterward (this will remove the frame from its parents child list). If you just hide the frame without this additional step, frames created afterward will get a higher [[FrameLevel|framelevel]] than the hidden one. After a while, you will get frames at maximum [[FrameLevel|framelevel]] which are likely to be drawn in a distorted way (false order caused by equal [[FrameLevel|framelevel]]).