WoW:API GetMapInfo: Difference between revisions

From AddOn Studio
Jump to navigation Jump to search
No edit summary
m (converted page to use {{wowapi}})
Line 1: Line 1:
<center>'''GetMapInfo''' ''-Documentation by [[user:Flickering|Flickering]]-''</center>
{{wowapi}} __NOTOC__


  mapFileName, textureHeight, textureWidth = GetMapInfo();
  mapFileName, textureHeight, textureWidth = GetMapInfo();
Line 22: Line 22:


Note that the width and height aren't in a consistent order with most of the other API functions. Neither of the values are used by the UI so it's impossible to tell whether this is a deliberate inconsistency or a typo! The return values would appear to imply they are, however, reversed from the usual width, height convention. -- [[User:Flickering|Flickering]] 16:42, 26 Dec 2004 (EST)
Note that the width and height aren't in a consistent order with most of the other API functions. Neither of the values are used by the UI so it's impossible to tell whether this is a deliberate inconsistency or a typo! The return values would appear to imply they are, however, reversed from the usual width, height convention. -- [[User:Flickering|Flickering]] 16:42, 26 Dec 2004 (EST)
----
{{WoW API}}

Revision as of 19:18, 23 June 2006

WoW API < GetMapInfo

mapFileName, textureHeight, textureWidth = GetMapInfo();

Return the map information about the current world map texture.


Arguments
none

Returns
mapFileName, textureHeight, textureWidth
mapFileName
String - The name of the file containing the textures for the current world map (nil for the whole world, BUT the official API catches this with a comment of Temporary Hack and uses the value "World" instead!)
textureHeight
Number - The height of the specified texture (0 if no texture)
textureWidth
Number - The width of the specified texture (0 if no texture) (This is a guess, it's not used in the UI)

DetailsP

Note that the width and height aren't in a consistent order with most of the other API functions. Neither of the values are used by the UI so it's impossible to tell whether this is a deliberate inconsistency or a typo! The return values would appear to imply they are, however, reversed from the usual width, height convention. -- Flickering 16:42, 26 Dec 2004 (EST)