OnDgsMouseClickDown - Revision history

Thisdp at 14:41, 18 February 2021

2021-02-18T14:41:51Z

← Older revision		Revision as of 14:41, 18 February 2021
Line 10:		Line 10:
	==Parameters==		==Parameters==
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	string button, int absoluteX, int absoluteY		string button, string state, int absoluteX, int absoluteY, bool isCoolingDown
	</syntaxhighlight>		</syntaxhighlight>
	*'''button:''' the name of the button which will be clicked , it can be ''left'', ''right'', ''middle''		*'''button''': the name of the button which will be clicked , it can be ''left'', ''right'', ''middle''.
	*'''absoluteX:''' the X position of the mouse cursor, in pixels, measured from the left side of the screen.		*'''state''': a string of mouse state. In this cause, it is always '''down'''.
	*'''absoluteY:''' the Y position of the mouse cursor, in pixels, measured from the top of the screen.		*'''absoluteX''': the X position of the mouse cursor, in pixels, measured from the left side of the screen.
	*'''isCoolingDown:''' A bool indicates whether this dgs element is cooling down. See [[DGS_General_Basic_Properties#clickCoolDown\|Property:clickCoolDown]]		*'''absoluteY''': the Y position of the mouse cursor, in pixels, measured from the top of the screen.
			*'''isCoolingDown''': A bool indicates whether this dgs element is cooling down. See [[DGS_General_Basic_Properties#clickCoolDown\|Property:clickCoolDown]]

	==Source==		==Source==

Thisdp at 14:16, 16 February 2021

2021-02-16T14:16:05Z

← Older revision		Revision as of 14:16, 16 February 2021
Line 6:		Line 6:
	{{Note\|The '''player''' who clicked the dgs-element is always the [[localPlayer]].}}		{{Note\|The '''player''' who clicked the dgs-element is always the [[localPlayer]].}}
	{{Note\|If you want to ask why everything is triggered... See the forth parameter of [[addEventHandler]]}}		{{Note\|If you want to ask why everything is triggered... See the forth parameter of [[addEventHandler]]}}
	{{Note\|This event will not trigger when [[~~onDgsMouseClick~~]] is cancelled.}}		{{Note\|This event will not trigger when [[onDgsMousePreClick]] is cancelled.}}

	==Parameters==		==Parameters==

Thisdp at 11:46, 12 February 2021

2021-02-12T11:46:38Z

← Older revision		Revision as of 11:46, 12 February 2021
Line 6:		Line 6:
	{{Note\|The '''player''' who clicked the dgs-element is always the [[localPlayer]].}}		{{Note\|The '''player''' who clicked the dgs-element is always the [[localPlayer]].}}
	{{Note\|If you want to ask why everything is triggered... See the forth parameter of [[addEventHandler]]}}		{{Note\|If you want to ask why everything is triggered... See the forth parameter of [[addEventHandler]]}}
			{{Note\|This event will not trigger when [[onDgsMouseClick]] is cancelled.}}

	==Parameters==		==Parameters==

Thisdp at 11:44, 12 February 2021

2021-02-12T11:44:21Z

← Older revision		Revision as of 11:44, 12 February 2021
Line 14:		Line 14:
	*'''absoluteX:''' the X position of the mouse cursor, in pixels, measured from the left side of the screen.		*'''absoluteX:''' the X position of the mouse cursor, in pixels, measured from the left side of the screen.
	*'''absoluteY:''' the Y position of the mouse cursor, in pixels, measured from the top of the screen.		*'''absoluteY:''' the Y position of the mouse cursor, in pixels, measured from the top of the screen.
			*'''isCoolingDown:''' A bool indicates whether this dgs element is cooling down. See [[DGS_General_Basic_Properties#clickCoolDown\|Property:clickCoolDown]]

	==Source==		==Source==

Deihim007 at 19:20, 16 October 2019

2019-10-16T19:20:34Z

← Older revision		Revision as of 19:20, 16 October 2019
Line 9:		Line 9:
	==Parameters==		==Parameters==
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	string button~~, string state~~, int absoluteX, int absoluteY		string button, int absoluteX, int absoluteY
	</syntaxhighlight>		</syntaxhighlight>
	*'''button:''' the name of the button which will be clicked , it can be ''left'', ''right'', ''middle''		*'''button:''' the name of the button which will be clicked , it can be ''left'', ''right'', ''middle''

Thisdp at 06:52, 16 August 2019

2019-08-16T06:52:38Z

← Older revision		Revision as of 06:52, 16 August 2019
Line 3:		Line 3:
	This event happens when any dgs-element clicked ( Mouse down ).		This event happens when any dgs-element clicked ( Mouse down ).

	And this event is for ~~those who are lazy to use judgment statement ( if state == "down" ) and~~ those who are converting gui to dgs.		And this event is for those who are converting gui to dgs.
	{{Note\|The '''player''' who clicked the dgs-element is always the [[localPlayer]].}}		{{Note\|The '''player''' who clicked the dgs-element is always the [[localPlayer]].}}
	{{Note\|If you want to ask why everything is triggered... See the forth parameter of [[addEventHandler]]}}		{{Note\|If you want to ask why everything is triggered... See the forth parameter of [[addEventHandler]]}}

Thisdp at 06:51, 16 August 2019

2019-08-16T06:51:29Z

← Older revision		Revision as of 06:51, 16 August 2019
Line 12:		Line 12:
	</syntaxhighlight>		</syntaxhighlight>
	*'''button:''' the name of the button which will be clicked , it can be ''left'', ''right'', ''middle''		*'''button:''' the name of the button which will be clicked , it can be ''left'', ''right'', ''middle''
	*'''state:''' the state of the mouse button, will be "down"
	*'''absoluteX:''' the X position of the mouse cursor, in pixels, measured from the left side of the screen.		*'''absoluteX:''' the X position of the mouse cursor, in pixels, measured from the left side of the screen.
	*'''absoluteY:''' the Y position of the mouse cursor, in pixels, measured from the top of the screen.		*'''absoluteY:''' the Y position of the mouse cursor, in pixels, measured from the top of the screen.
Line 37:		Line 36:

	-- Setup our function to output the message to the chatbox		-- Setup our function to output the message to the chatbox
	function outputEditBox ( button~~, state~~ )		function outputEditBox ( button )
	if button == "left" then		if button == "left" then
	local text = DGS:dgsGetText( editBox )-- Get the text from the edit box		local text = DGS:dgsGetText( editBox )-- Get the text from the edit box
Line 51:		Line 50:
	btnOutput = DGS:dgsCreateButton( 0.7, 0.1, 0.2, 0.1, "Output!", true )		btnOutput = DGS:dgsCreateButton( 0.7, 0.1, 0.2, 0.1, "Output!", true )

	function outputEditBox ( button~~, state~~ )		function outputEditBox ( button )
	if button == "left" then		if button == "left" then
	outputChatBox ( "Hey bro, you clicked me, your state is "..state )		outputChatBox ( "Hey bro, you clicked me, your state is "..state )

Thisdp at 15:05, 22 July 2019

2019-07-22T15:05:57Z

← Older revision		Revision as of 15:05, 22 July 2019
Line 4:		Line 4:

	And this event is for those who are lazy to use judgment statement ( if state == "down" ) and those who are converting gui to dgs.		And this event is for those who are lazy to use judgment statement ( if state == "down" ) and those who are converting gui to dgs.

	{{Note\|The '''player''' who clicked the dgs-element is always the [[localPlayer]].}}		{{Note\|The '''player''' who clicked the dgs-element is always the [[localPlayer]].}}
	{{Note\|If you want to ask why everything is triggered... See the forth parameter of [[addEventHandler]]}}		{{Note\|If you want to ask why everything is triggered... See the forth parameter of [[addEventHandler]]}}

Thisdp at 15:05, 22 July 2019

2019-07-22T15:05:46Z

← Older revision		Revision as of 15:05, 22 July 2019
Line 2:		Line 2:
	__NOTOC__		__NOTOC__
	This event happens when any dgs-element clicked ( Mouse down ).		This event happens when any dgs-element clicked ( Mouse down ).

	And this event is for those who are lazy to use judgment statement ( if state == "down" ) and those who are converting gui to dgs.		And this event is for those who are lazy to use judgment statement ( if state == "down" ) and those who are converting gui to dgs.

	{{Note\|The '''player''' who clicked the dgs-element is always the [[localPlayer]].}}		{{Note\|The '''player''' who clicked the dgs-element is always the [[localPlayer]].}}
	{{Note\|If you want to ask why everything is triggered... See the forth parameter of [[addEventHandler]]}}		{{Note\|If you want to ask why everything is triggered... See the forth parameter of [[addEventHandler]]}}

Thisdp: Created page with "{{Client event}} NOTOC This event happens when any dgs-element clicked ( Mouse down ). And this event is for those who are lazy to use judgment statement ( if state == "do..."

2019-07-22T15:04:54Z

Created page with "{{Client event}} __NOTOC__ This event happens when any dgs-element clicked ( Mouse down ). And this event is for those who are lazy to use judgment statement ( if state == "do..."

New page

{{Client event}}
__NOTOC__
This event happens when any dgs-element clicked ( Mouse down ).
And this event is for those who are lazy to use judgment statement ( if state == "down" ) and those who are converting gui to dgs.
{{Note|The '''player''' who clicked the dgs-element is always the [[localPlayer]].}}
{{Note|If you want to ask why everything is triggered... See the forth parameter of [[addEventHandler]]}}

==Parameters==
<syntaxhighlight lang="lua">
string button, string state, int absoluteX, int absoluteY
</syntaxhighlight>
*'''button:''' the name of the button which will be clicked , it can be ''left'', ''right'', ''middle''
*'''state:''' the state of the mouse button, will be "down"
*'''absoluteX:''' the X position of the mouse cursor, in pixels, measured from the left side of the screen.
*'''absoluteY:''' the Y position of the mouse cursor, in pixels, measured from the top of the screen.

==Source==
The [[event system#Event source|source]] of this event is the DGS element that was clicked.

==Example==
This example creates an edit box alongside an "Output!" button. When the button is clicked with the left mouse button, it will output the message in the edit box into the chat box.
<syntaxhighlight lang="lua">
DGS = exports.dgs
-- When client's resource starts, create the GUI
function initGUI( )
-- Create our button
btnOutput = DGS:dgsCreateButton( 0.7, 0.1, 0.2, 0.1, "Output!", true )

-- And attach our button to the outputEditBox function
addEventHandler ( "onDgsMouseClickDown", btnOutput, outputEditBox )

-- Create an edit box and define it as "editBox".
editBox = DGS:dgsCreateEdit( 0.3, 0.1, 0.4, 0.1, "Type your message here!", true )
end
addEventHandler( "onClientResourceStart", getResourceRootElement( getThisResource( ) ), initGUI )

-- Setup our function to output the message to the chatbox
function outputEditBox ( button, state )
if button == "left" then
local text = DGS:dgsGetText( editBox )-- Get the text from the edit box
outputChatBox ( text ) -- Output that text
end
end
</syntaxhighlight>

===Clear Example===
<syntaxhighlight lang="lua">
DGS = exports.dgs

btnOutput = DGS:dgsCreateButton( 0.7, 0.1, 0.2, 0.1, "Output!", true )

function outputEditBox ( button, state )
if button == "left" then
outputChatBox ( "Hey bro, you clicked me, your state is "..state )
end
end
addEventHandler ( "onDgsMouseClickDown", btnOutput, outputEditBox )
</syntaxhighlight>

==See Also==
===DGS events===
{{DGSEVENTS}}

OnDgsMouseClickDown - Revision history

Thisdp at 14:41, 18 February 2021

Thisdp at 14:16, 16 February 2021

Thisdp at 11:46, 12 February 2021

Thisdp at 11:44, 12 February 2021

Deihim007 at 19:20, 16 October 2019

Thisdp at 06:52, 16 August 2019

Thisdp at 06:51, 16 August 2019

Thisdp at 15:05, 22 July 2019

Thisdp at 15:05, 22 July 2019

Thisdp: Created page with "{{Client event}} __NOTOC__ This event happens when any dgs-element clicked ( Mouse down ). And this event is for those who are lazy to use judgment statement ( if state == "do..."

Thisdp: Created page with "{{Client event}} NOTOC This event happens when any dgs-element clicked ( Mouse down ). And this event is for those who are lazy to use judgment statement ( if state == "do..."