GetCursorPosition - Revision history

Fernando187: /* See Also */

2024-11-06T15:11:16Z

2022-04-09T21:22:56Z

Return RELATIVE screen coordinates, not absolute

← Older revision		Revision as of 21:22, 9 April 2022
Line 9:		Line 9:

	===Returns===		===Returns===
	Returns 5 values: ''cursorX'', ''cursorY'', ''worldX'', ''worldY'', ''worldZ''. The first two values are the 2D '''~~absolute~~''' screen coordinates of the cursor. The 3 values that follow are the 3D world map coordinates that the cursor points at. If the cursor isn't showing, returns ''false'' as the first value.		Returns 5 values: ''cursorX'', ''cursorY'', ''worldX'', ''worldY'', ''worldZ''. The first two values are the 2D '''relative''' screen coordinates of the cursor. The 3 values that follow are the 3D world map coordinates that the cursor points at. If the cursor isn't showing, returns ''false'' as the first value.

	===Issues===		===Issues===

2022-01-30T10:15:23Z

Updated issues

← Older revision		Revision as of 10:15, 30 January 2022
Line 13:		Line 13:
	===Issues===		===Issues===
	{{Issues\|		{{Issues\|
	{{Issue\|~~5226~~\|getCursorPosition() ~~3D Positions Return Inaccurate, But Nearby Positions - Also Negative WorldZ~~}}		{{Issue\|1166\|getCursorPosition() returns false even when cursor is showing due to opened console}}
	}}		}}

2022-01-16T19:02:14Z

GetCursorPosition returns ABSOLUTE values instead of relative ones.

← Older revision		Revision as of 19:02, 16 January 2022
Line 9:		Line 9:

	===Returns===		===Returns===
	Returns 5 values: ''cursorX'', ''cursorY'', ''worldX'', ''worldY'', ''worldZ''. The first two values are the 2D ~~relative screen coordinates of the cursor:~~ ''~~cursorX~~'' ~~goes from 0 (left side~~ of the ~~screen) to 1 (right side), ''cursorY'' goes from 0 (top) to 1 (bottom)~~. The 3 values that follow are the 3D world map coordinates that the cursor points at. If the cursor isn't showing, returns ''false'' as the first value.		Returns 5 values: ''cursorX'', ''cursorY'', ''worldX'', ''worldY'', ''worldZ''. The first two values are the 2D '''absolute''' screen coordinates of the cursor. The 3 values that follow are the 3D world map coordinates that the cursor points at. If the cursor isn't showing, returns ''false'' as the first value.

	===Issues===		===Issues===

2019-02-24T13:49:09Z

Reverted edits by Andrasxa (talk) to last revision by Surge

2019-02-24T12:38:38Z

2018-10-10T14:33:19Z

2018-04-25T11:42:34Z

Syntax

← Older revision		Revision as of 11:42, 25 April 2018
Line 5:		Line 5:
	==Syntax==		==Syntax==
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	float float float float float getCursorPosition ( )		float, float, float, float, float getCursorPosition ( )
	</syntaxhighlight>		</syntaxhighlight>

2018-03-15T21:19:55Z

Example

← Older revision		Revision as of 21:19, 15 March 2018
Line 34:		Line 34:

	This (untested) example uses [[processLineOfSight]] to calculate the exact world location:		This (untested) example uses [[processLineOfSight]] to calculate the exact world location:
			'''Warning, using the script down there will cause high CPU usage.'''
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	addEventHandler( "onClientRender", root,		addEventHandler( "onClientRender", root,

2018-03-15T21:18:54Z

Example

← Older revision		Revision as of 21:18, 15 March 2018
Line 20:		Line 20:
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	function cursorInfo()		function cursorInfo()
	~~local showing =~~ isCursorShowing ()		if isCursorShowing() then -- if the cursor is showing
	~~if showing~~ then -- if the cursor is showing
	local screenx, screeny, worldx, worldy, worldz = getCursorPosition()		local screenx, screeny, worldx, worldy, worldz = getCursorPosition()