WoW:UI coordinates - Revision history

Move page script: Move page script moved page UI coordinates to WoW:UI coordinates without leaving a redirect

2023-08-15T04:49:01Z

Move page script moved page UI coordinates to UI coordinates without leaving a redirect

← Older revision

Revision as of 04:49, 15 August 2023

WoWWiki>PProvost at 04:15, 3 January 2009

2009-01-03T04:15:57Z

← Older revision		Revision as of 04:15, 3 January 2009
Line 51:		Line 51:
	and ((frameB:GetBottom()sB) < (frameA:GetTop()sA));		and ((frameB:GetBottom()sB) < (frameA:GetTop()sA));
	end		end

	~~== External Links ==~~

	[[http://www.wowplotter.com wowplotter.com]] - WoWPlotter plots quest UI coordinates on their corresponding maps, and can also find other nearby quests so you can do them at the same time, all without an addon.

WoWWiki>Pcj at 17:19, 17 January 2008

2008-01-17T17:19:46Z

← Older revision		Revision as of 17:19, 17 January 2008
Line 1:		Line 1:
	{{uitech}}~~{{tocright}}~~		{{uitech}}


	The WoW User Interface engine is designed to provide a consistent UI look regardless of screen shape or resolution, and thus scaling is a pervasive part of the WoW User Interface. While this is generally transparent to users of the game, it can cause some confusion for developers, since different sets of functions operate with different scaled coordinate systems. This document tries to provide consistent naming and a description of each one.		The WoW User Interface engine is designed to provide a consistent UI look regardless of screen shape or resolution, and thus scaling is a pervasive part of the WoW User Interface. While this is generally transparent to users of the game, it can cause some confusion for developers, since different sets of functions operate with different scaled coordinate systems. This document tries to provide consistent naming and a description of each one.

WoWWiki>Pacman420 at 03:18, 26 November 2007

2007-11-26T03:18:16Z

← Older revision		Revision as of 03:18, 26 November 2007
Line 52:		Line 52:
	and ((frameB:GetBottom()sB) < (frameA:GetTop()sA));		and ((frameB:GetBottom()sB) < (frameA:GetTop()sA));
	end		end

			== External Links ==

			[[http://www.wowplotter.com wowplotter.com]] - WoWPlotter plots quest UI coordinates on their corresponding maps, and can also find other nearby quests so you can do them at the same time, all without an addon.

WoWWiki>Hobinbot: demoted headings

2007-01-08T14:51:21Z

demoted headings

← Older revision		Revision as of 14:51, 8 January 2007
Line 5:		Line 5:


	= Origin and Axes =		== Origin and Axes ==
	The origin is generally the BOTTOM LEFT corner of the screen. X coordinates always increase to the RIGHT (and decrease LEFT), and Y coordinates always increase UP (and decrease DOWN).		The origin is generally the BOTTOM LEFT corner of the screen. X coordinates always increase to the RIGHT (and decrease LEFT), and Y coordinates always increase UP (and decrease DOWN).


	= Coordinate Systems =		== Coordinate Systems ==

	== Real Screen Coordinates ==		=== Real Screen Coordinates ===
	The actual SIZE of the user's screen isn't readily available from the game, though you can query the current video settings for users that are not playing in windowed mode, to find out. Windowed mode presents somewhat of a challenge, because there the video settings determine the shape of the window, but the user can resize it on screen to whatever height or width they wish. It's best to just forget all about the real screen size anyway, and concentrate instead on the UI Root Coordinates:		The actual SIZE of the user's screen isn't readily available from the game, though you can query the current video settings for users that are not playing in windowed mode, to find out. Windowed mode presents somewhat of a challenge, because there the video settings determine the shape of the window, but the user can resize it on screen to whatever height or width they wish. It's best to just forget all about the real screen size anyway, and concentrate instead on the UI Root Coordinates:

	== UI Root Coordinates ==		=== UI Root Coordinates ===
	WoW normalizes all screen resolutions to be 768 pixels high, and then an aspect-appropriate width. Thus any 4:3 screen resolution appears as 1024x768, any 5:4 as 960x768, and 16:10 as 1228.8x768. The virtual "root" frame, which all non-parented frames are children of, then has this normalized size.		WoW normalizes all screen resolutions to be 768 pixels high, and then an aspect-appropriate width. Thus any 4:3 screen resolution appears as 1024x768, any 5:4 as 960x768, and 16:10 as 1228.8x768. The virtual "root" frame, which all non-parented frames are children of, then has this normalized size.

Line 21:		Line 21:
	(Prior to WoW 2.0, for frames with anchor-defined sizes (not forced sizes), [[API LayoutFrame GetWidth\|w = layoutFrame:GetWidth()]] and [[API LayoutFrame GetHeight\|h = layoutFrame:GetHeight()]] return values in the UI Root Coordinate system.)		(Prior to WoW 2.0, for frames with anchor-defined sizes (not forced sizes), [[API LayoutFrame GetWidth\|w = layoutFrame:GetWidth()]] and [[API LayoutFrame GetHeight\|h = layoutFrame:GetHeight()]] return values in the UI Root Coordinate system.)

	== Frame Scaled Coordinates ==		=== Frame Scaled Coordinates ===
	Most frame-specific coordinate functions operate in a coordinate system that is adjusted by the Frame's effective scale (As returned by [[API Frame GetEffectiveScale\|effScale = frame:GetEffectiveScale()]]. Each unit in the frame scaled coordinate system corresponds to effScale units in the UI Root coordinate system. The origin, however, is still the BOTTOM LEFT corner of the screen.		Most frame-specific coordinate functions operate in a coordinate system that is adjusted by the Frame's effective scale (As returned by [[API Frame GetEffectiveScale\|effScale = frame:GetEffectiveScale()]]. Each unit in the frame scaled coordinate system corresponds to effScale units in the UI Root coordinate system. The origin, however, is still the BOTTOM LEFT corner of the screen.

Line 31:		Line 31:


	= Useful Code Snippets =		== Useful Code Snippets ==

	== Cursor Over Frame ==		=== Cursor Over Frame ===

	function MouseIsOver(frame)		function MouseIsOver(frame)
Line 43:		Line 43:
	end		end

	== Frame Overlap ==		=== Frame Overlap ===

	function FramesOverlap(frameA, frameB)		function FramesOverlap(frameA, frameB)

WoWWiki>Flickering: Updated GetWidth/GetHeight details.

2006-12-19T04:03:25Z

Updated GetWidth/GetHeight details.

← Older revision		Revision as of 04:03, 19 December 2006
Line 19:		Line 19:
	The [[API GetCursorPosition\|x,y = GetCursorPosition()]] function returns the x,y location in UI Root Coordinates, with the origin in its standard BOTTOM LEFT screen corner location.		The [[API GetCursorPosition\|x,y = GetCursorPosition()]] function returns the x,y location in UI Root Coordinates, with the origin in its standard BOTTOM LEFT screen corner location.

	~~Currently~~, for frames with anchor-defined sizes (not forced sizes), [[API LayoutFrame GetWidth\|w = layoutFrame:GetWidth()]] and [[API LayoutFrame GetHeight\|h = layoutFrame:GetHeight()]] return values in the UI Root Coordinate system.		(Prior to WoW 2.0, for frames with anchor-defined sizes (not forced sizes), [[API LayoutFrame GetWidth\|w = layoutFrame:GetWidth()]] and [[API LayoutFrame GetHeight\|h = layoutFrame:GetHeight()]] return values in the UI Root Coordinate system.)

	== Frame Scaled Coordinates ==		== Frame Scaled Coordinates ==
	Most frame-specific coordinate functions operate in a coordinate system that is adjusted by the Frame's effective scale (As returned by [[API Frame GetEffectiveScale\|effScale = frame:GetEffectiveScale()]]. Each unit in the frame scaled coordinate system corresponds to effScale units in the UI Root coordinate system. The origin, however, is still the BOTTOM LEFT corner of the screen.		Most frame-specific coordinate functions operate in a coordinate system that is adjusted by the Frame's effective scale (As returned by [[API Frame GetEffectiveScale\|effScale = frame:GetEffectiveScale()]]. Each unit in the frame scaled coordinate system corresponds to effScale units in the UI Root coordinate system. The origin, however, is still the BOTTOM LEFT corner of the screen.

	The main methods which return values in Frame Scaled Coordinates are [[API Frame GetLeft\|x = frame:GetLeft()]], [[API Frame GetRight\|x = frame:GetRight()]], [[API Frame GetBottom\|y = frame:GetBottom()]], [[API Frame GetTop\|y = frame:GetTop()]], ~~and~~ [[API Frame GetCenter\|x,y = frame:GetCenter()]].		The main methods which return values in Frame Scaled Coordinates are [[API Frame GetLeft\|x = frame:GetLeft()]], [[API Frame GetRight\|x = frame:GetRight()]], [[API Frame GetBottom\|y = frame:GetBottom()]], [[API Frame GetTop\|y = frame:GetTop()]], [[API Frame GetCenter\|x,y = frame:GetCenter()]], and [[API Frame GetRect\|l,b,w,h = frame:GetRect()]]

	In addition, anchor offsets, as controlled by [[API LayoutFrame SetPoint\|layoutFrame:SetPoint("POINT","RelativeFrame","RELPOINT",x,y)]] and the anchoring XML elements, are also specified in the Frame Scaled coordinate system of the point that is being anchored, but are relative to the attachment point on the relative frame. This can sometimes have surprising results if the layoutFrame and RelativeFrame have different effective scales.		In addition, anchor offsets, as controlled by [[API LayoutFrame SetPoint\|layoutFrame:SetPoint("POINT","RelativeFrame","RELPOINT",x,y)]] and the anchoring XML elements, are also specified in the Frame Scaled coordinate system of the point that is being anchored, but are relative to the attachment point on the relative frame. This can sometimes have surprising results if the layoutFrame and RelativeFrame have different effective scales.

	~~Currently, for frames with explicit sizes (not anchor defined),~~ [[API LayoutFrame GetWidth\|w = layoutFrame:GetWidth()]] and [[API LayoutFrame GetHeight\|h = layoutFrame:GetHeight()]] return values in the Frame Scaled coordinate system, and the corresponding set functions [[API LayoutFrame SetWidth\|layoutFrame:SetWidth(w)]], and [[API LayoutFrame SetWidth\|layoutFrame:SetHeight(h)]] take values in the Frame Scaled coordinate system.		[[API LayoutFrame GetWidth\|w = layoutFrame:GetWidth()]] and [[API LayoutFrame GetHeight\|h = layoutFrame:GetHeight()]] return values in the Frame Scaled coordinate system, and the corresponding set functions [[API LayoutFrame SetWidth\|layoutFrame:SetWidth(w)]], and [[API LayoutFrame SetWidth\|layoutFrame:SetHeight(h)]] take values in the Frame Scaled coordinate system.

WoWWiki>Mikk: {{uitech}}, formatting...

2006-06-17T09:02:39Z

{{uitech}}, formatting...

← Older revision		Revision as of 09:02, 17 June 2006
Line 1:		Line 1:
	{{tocright}}		{{uitech}}{{tocright}}


	The WoW User Interface engine is designed to provide a consistent UI look regardless of screen shape or resolution, and thus scaling is a pervasive part of the WoW User Interface. While this is generally transparent to users of the game, it can cause some confusion for developers, since different sets of functions operate with different scaled coordinate systems. This document tries to provide consistent naming and a description of each one.		The WoW User Interface engine is designed to provide a consistent UI look regardless of screen shape or resolution, and thus scaling is a pervasive part of the WoW User Interface. While this is generally transparent to users of the game, it can cause some confusion for developers, since different sets of functions operate with different scaled coordinate systems. This document tries to provide consistent naming and a description of each one.


	= Origin and Axes =		= Origin and Axes =
	The origin is generally the BOTTOM LEFT corner of the screen. X coordinates always increase to the RIGHT (and decrease LEFT), and Y coordinates always increase UP (and decrease DOWN).		The origin is generally the BOTTOM LEFT corner of the screen. X coordinates always increase to the RIGHT (and decrease LEFT), and Y coordinates always increase UP (and decrease DOWN).


	= Coordinate Systems =		= Coordinate Systems =
Line 25:		Line 29:

	Currently, for frames with explicit sizes (not anchor defined), [[API LayoutFrame GetWidth\|w = layoutFrame:GetWidth()]] and [[API LayoutFrame GetHeight\|h = layoutFrame:GetHeight()]] return values in the Frame Scaled coordinate system, and the corresponding set functions [[API LayoutFrame SetWidth\|layoutFrame:SetWidth(w)]], and [[API LayoutFrame SetWidth\|layoutFrame:SetHeight(h)]] take values in the Frame Scaled coordinate system.		Currently, for frames with explicit sizes (not anchor defined), [[API LayoutFrame GetWidth\|w = layoutFrame:GetWidth()]] and [[API LayoutFrame GetHeight\|h = layoutFrame:GetHeight()]] return values in the Frame Scaled coordinate system, and the corresponding set functions [[API LayoutFrame SetWidth\|layoutFrame:SetWidth(w)]], and [[API LayoutFrame SetWidth\|layoutFrame:SetHeight(h)]] take values in the Frame Scaled coordinate system.


	= Useful Code Snippets =		= Useful Code Snippets =
Line 47:		Line 52:
	and ((frameB:GetBottom()sB) < (frameA:GetTop()sA));		and ((frameB:GetBottom()sB) < (frameA:GetTop()sA));
	end		end


	~~[[Category:UI Technical Details]]~~

WoWWiki>Flickering at 23:55, 23 February 2006

2006-02-23T23:55:09Z

New page

{{tocright}}
The WoW User Interface engine is designed to provide a consistent UI look regardless of screen shape or resolution, and thus scaling is a pervasive part of the WoW User Interface. While this is generally transparent to users of the game, it can cause some confusion for developers, since different sets of functions operate with different scaled coordinate systems. This document tries to provide consistent naming and a description of each one.

= Origin and Axes =
The origin is generally the BOTTOM LEFT corner of the screen. X coordinates always increase to the RIGHT (and decrease LEFT), and Y coordinates always increase UP (and decrease DOWN).

= Coordinate Systems =

== Real Screen Coordinates ==
The actual SIZE of the user's screen isn't readily available from the game, though you can query the current video settings for users that are not playing in windowed mode, to find out. Windowed mode presents somewhat of a challenge, because there the video settings determine the shape of the window, but the user can resize it on screen to whatever height or width they wish. It's best to just forget all about the real screen size anyway, and concentrate instead on the UI Root Coordinates:

== UI Root Coordinates ==
WoW normalizes all screen resolutions to be 768 pixels high, and then an aspect-appropriate width. Thus any 4:3 screen resolution appears as 1024x768, any 5:4 as 960x768, and 16:10 as 1228.8x768. The virtual "root" frame, which all non-parented frames are children of, then has this normalized size.

The [[API GetCursorPosition|x,y = GetCursorPosition()]] function returns the x,y location in UI Root Coordinates, with the origin in its standard BOTTOM LEFT screen corner location.

Currently, for frames with anchor-defined sizes (not forced sizes), [[API LayoutFrame GetWidth|w = layoutFrame:GetWidth()]] and [[API LayoutFrame GetHeight|h = layoutFrame:GetHeight()]] return values in the UI Root Coordinate system.

== Frame Scaled Coordinates ==
Most frame-specific coordinate functions operate in a coordinate system that is adjusted by the Frame's effective scale (As returned by [[API Frame GetEffectiveScale|effScale = frame:GetEffectiveScale()]]. Each unit in the frame scaled coordinate system corresponds to effScale units in the UI Root coordinate system. The origin, however, is still the BOTTOM LEFT corner of the screen.

The main methods which return values in Frame Scaled Coordinates are [[API Frame GetLeft|x = frame:GetLeft()]], [[API Frame GetRight|x = frame:GetRight()]], [[API Frame GetBottom|y = frame:GetBottom()]], [[API Frame GetTop|y = frame:GetTop()]], and [[API Frame GetCenter|x,y = frame:GetCenter()]].

In addition, anchor offsets, as controlled by [[API LayoutFrame SetPoint|layoutFrame:SetPoint("POINT","RelativeFrame","RELPOINT",x,y)]] and the anchoring XML elements, are also specified in the Frame Scaled coordinate system of the point that is being anchored, but are relative to the attachment point on the relative frame. This can sometimes have surprising results if the layoutFrame and RelativeFrame have different effective scales.

Currently, for frames with explicit sizes (not anchor defined), [[API LayoutFrame GetWidth|w = layoutFrame:GetWidth()]] and [[API LayoutFrame GetHeight|h = layoutFrame:GetHeight()]] return values in the Frame Scaled coordinate system, and the corresponding set functions [[API LayoutFrame SetWidth|layoutFrame:SetWidth(w)]], and [[API LayoutFrame SetWidth|layoutFrame:SetHeight(h)]] take values in the Frame Scaled coordinate system.

= Useful Code Snippets =

== Cursor Over Frame ==

function MouseIsOver(frame)
local x, y = GetCursorPosition();
local s = frame:GetEffectiveScale();
x, y = x/s, y/s;
return ((x >= frame:GetLeft()) and (x <= frame:GetRight())
and (y >= frame:GetBottom()) and (y <= frame:GetTop()));
end

== Frame Overlap ==

function FramesOverlap(frameA, frameB)
local sA, sB = frameA:GetEffectiveScale(), frameB:GetEffectiveScale();
return ((frameA:GetLeft()*sA) < (frameB:GetRight()*sB))
and ((frameB:GetLeft()*sB) < (frameA:GetRight()*sA))
and ((frameA:GetBottom()*sA) < (frameB:GetTop()*sB))
and ((frameB:GetBottom()*sB) < (frameA:GetTop()*sA));
end

[[Category:UI Technical Details]]