OnDgsBlur - Revision history

Thisdp: Thisdp moved page OnClientDgsDxBlur to OnDgsBlur

2018-01-20T13:39:31Z

Thisdp moved page OnClientDgsDxBlur to OnDgsBlur

← Older revision

Revision as of 13:39, 20 January 2018

Thisdp: /* Notes */

2018-01-20T13:38:14Z

Notes

← Older revision		Revision as of 13:38, 20 January 2018
Line 44:		Line 44:

	==Notes==		==Notes==
	*When the focus is transfered from one DGS element to an other, it is guaranteed that ''onDgsBlur'' on the element that lost focus is triggered before [[~~Dgs/~~onDgsBlur\|onDgsBlur]] on the element that just gained focus		*When the focus is transfered from one DGS element to an other, it is guaranteed that ''onDgsBlur'' on the element that lost focus is triggered before [[onDgsBlur\|onDgsBlur]] on the element that just gained focus
	*When the focus of a full window is lost (transfered to an other window or lost), ''onDgsBlur'' is only triggered for the window itself even if one of its widgets had focus too. It's important in this case to use the 4th parameter of [[addEventHandler]] if you are only registered for the events of a child widget (cf. Example)		*When the focus of a full window is lost (transfered to an other window or lost), ''onDgsBlur'' is only triggered for the window itself even if one of its widgets had focus too. It's important in this case to use the 4th parameter of [[addEventHandler]] if you are only registered for the events of a child widget (cf. Example)
	*When a window is hidden with [[DgsSetVisible\|dgsSetVisible]], it (or its child widget having focus) keeps focus internally until an other window gains focus or the chatbox is used		*When a window is hidden with [[DgsSetVisible\|dgsSetVisible]], it (or its child widget having focus) keeps focus internally until an other window gains focus or the chatbox is used

Thisdp: /* Notes */

2018-01-20T13:37:58Z

Notes

← Older revision		Revision as of 13:37, 20 January 2018
Line 46:		Line 46:
	*When the focus is transfered from one DGS element to an other, it is guaranteed that ''onDgsBlur'' on the element that lost focus is triggered before [[Dgs/onDgsBlur\|onDgsBlur]] on the element that just gained focus		*When the focus is transfered from one DGS element to an other, it is guaranteed that ''onDgsBlur'' on the element that lost focus is triggered before [[Dgs/onDgsBlur\|onDgsBlur]] on the element that just gained focus
	*When the focus of a full window is lost (transfered to an other window or lost), ''onDgsBlur'' is only triggered for the window itself even if one of its widgets had focus too. It's important in this case to use the 4th parameter of [[addEventHandler]] if you are only registered for the events of a child widget (cf. Example)		*When the focus of a full window is lost (transfered to an other window or lost), ''onDgsBlur'' is only triggered for the window itself even if one of its widgets had focus too. It's important in this case to use the 4th parameter of [[addEventHandler]] if you are only registered for the events of a child widget (cf. Example)
	*When a window is hidden with [[~~Dgs/~~DgsSetVisible\|dgsSetVisible]], it (or its child widget having focus) keeps focus internally until an other window gains focus or the chatbox is used		*When a window is hidden with [[DgsSetVisible\|dgsSetVisible]], it (or its child widget having focus) keeps focus internally until an other window gains focus or the chatbox is used

	==See Also==		==See Also==

Thisdp: /* Notes */

2018-01-20T13:37:41Z

Notes

← Older revision		Revision as of 13:37, 20 January 2018
Line 44:		Line 44:

	==Notes==		==Notes==
	*When the focus is transfered from one DGS element to an other, it is guaranteed that ''~~onClientDgsDxBlur~~'' on the element that lost focus is triggered before [[Dgs/~~onClientDgsDxBlur~~\|~~onClientDgsDxBlur~~]] on the element that just gained focus		*When the focus is transfered from one DGS element to an other, it is guaranteed that ''onDgsBlur'' on the element that lost focus is triggered before [[Dgs/onDgsBlur\|onDgsBlur]] on the element that just gained focus
	*When the focus of a full window is lost (transfered to an other window or lost), ''~~onClientDgsDxBlur~~'' is only triggered for the window itself even if one of its widgets had focus too. It's important in this case to use the 4th parameter of [[addEventHandler]] if you are only registered for the events of a child widget (cf. Example)		*When the focus of a full window is lost (transfered to an other window or lost), ''onDgsBlur'' is only triggered for the window itself even if one of its widgets had focus too. It's important in this case to use the 4th parameter of [[addEventHandler]] if you are only registered for the events of a child widget (cf. Example)
	*When a window is hidden with [[Dgs/~~DgsDxGUISetVisible~~\|~~dgsDxGUISetVisible~~]], it (or its child widget having focus) keeps focus internally until an other window gains focus or the chatbox is used		*When a window is hidden with [[Dgs/DgsSetVisible\|dgsSetVisible]], it (or its child widget having focus) keeps focus internally until an other window gains focus or the chatbox is used

	==See Also==		==See Also==

Thisdp: Undo revision 53758 by Thisdp (talk)

2018-01-20T13:37:04Z

Undo revision 53758 by Thisdp (talk)

@@ Line 1: / Line 1: @@
 local window, editbox = nil, nil
 DGS = exports.dgs
@@ Line 29: / Line 41: @@
 	end
 end

Thisdp at 13:36, 20 January 2018

2018-01-20T13:36:38Z

← Older revision		Revision as of 13:36, 20 January 2018
Line 1:		Line 1:
	~~{{Client event}}~~
	~~__NOTOC__~~
	~~This event is triggered each time a DGS element looses input focus (mainly useful for windows, editboxes and memos but triggered for all DGS elements nevertheless).~~

	~~==Parameters==~~
	~~''None''~~

	~~==Source==~~
	~~The [[event system#Event source\|source]] of this event is the DGS element which just lost input focus.~~

	~~==Example==~~
	~~<syntaxhighlight lang="lua">~~
	local window, editbox = nil, nil		local window, editbox = nil, nil
	DGS = exports.dgs		DGS = exports.dgs
Line 19:		Line 7:
	local left = screenWidth/2 - windowWidth/2		local left = screenWidth/2 - windowWidth/2
	local top = screenHeight/2 - windowHeight/2		local top = screenHeight/2 - windowHeight/2
	window = DGS:~~dgsDxCreateWindow~~(left, top, windowWidth, windowHeight, "Example Window", false)		window = DGS:dgsCreateWindow(left, top, windowWidth, windowHeight, "Example Window", false)
	editbox = DGS:~~dgsDxCreateEdit~~(11, 41, 241, 22, "", false, window)		editbox = DGS:dgsCreateEdit(11, 41, 241, 22, "", false, window)
	addEventHandler("~~onClientDgsDxFocus~~", editbox, ~~onClientDGSFocus_editbox~~, true) --true because for the example we want propagated events		addEventHandler("onDgsFocus", editbox, onDGSFocus_editbox, true) --true because for the example we want propagated events
	addEventHandler("~~onClientDgsDxBlur~~", editbox, ~~onClientDGSBlur_editbox~~, true) --true because for the example we want propagated events		addEventHandler("onDgsBlur", editbox, onDGSBlur_editbox, true) --true because for the example we want propagated events
	showCursor(true)		showCursor(true)
	end)		end)

	function ~~onClientDGSFocus_editbox~~()		function onDGSFocus_editbox()
	if source == editbox then		if source == editbox then
	outputChatBox("Example editBox received input focus")		outputChatBox("Example editBox received input focus")
Line 34:		Line 22:
	end		end

	function ~~onClientDGSBlur_editbox~~()		function onDGSBlur_editbox()
	if source == editbox then		if source == editbox then
	outputChatBox("Example editBox lost input focus")		outputChatBox("Example editBox lost input focus")
Line 41:		Line 29:
	end		end
	end		end
	~~</syntaxhighlight>~~

	~~==Notes==~~
	*When the focus is transfered from one DGS element to an other, it is guaranteed that ''onClientDgsDxBlur'' on the element that lost focus is triggered before [[Dgs/onClientDgsDxBlur\|onClientDgsDxBlur]] on the element that just gained focus
	*When the focus of a full window is lost (transfered to an other window or lost), ''onClientDgsDxBlur'' is only triggered for the window itself even if one of its widgets had focus too. It's important in this case to use the 4th parameter of [[addEventHandler]] if you are only registered for the events of a child widget (cf. Example)
	*When a window is hidden with [[Dgs/DgsDxGUISetVisible\|dgsDxGUISetVisible]], it (or its child widget having focus) keeps focus internally until an other window gains focus or the chatbox is used

	~~==See Also==~~
	~~===DGS events===~~
	~~{{DGSEVENTS}}~~
	~~===Client event functions===~~
	~~{{Client_event_functions}}~~

Thisdp: Thisdp moved page Dgs/onClientDgsDxBlur to OnClientDgsDxBlur

2017-07-02T02:14:05Z

Thisdp moved page Dgs/onClientDgsDxBlur to OnClientDgsDxBlur

← Older revision

Revision as of 02:14, 2 July 2017

Thisdp: /* Notes */

2017-06-25T09:21:50Z

Notes

← Older revision		Revision as of 09:21, 25 June 2017
Line 44:		Line 44:

	==Notes==		==Notes==
	*When the focus is transfered from one DGS element to an other, it is guaranteed that ''onClientDgsDxBlur'' on the element that lost focus is triggered before [[onClientDgsDxBlur]] on the element that just gained focus		*When the focus is transfered from one DGS element to an other, it is guaranteed that ''onClientDgsDxBlur'' on the element that lost focus is triggered before [[Dgs/onClientDgsDxBlur\|onClientDgsDxBlur]] on the element that just gained focus
	*When the focus of a full window is lost (transfered to an other window or lost), ''onClientDgsDxBlur'' is only triggered for the window itself even if one of its widgets had focus too. It's important in this case to use the 4th parameter of [[addEventHandler]] if you are only registered for the events of a child widget (cf. Example)		*When the focus of a full window is lost (transfered to an other window or lost), ''onClientDgsDxBlur'' is only triggered for the window itself even if one of its widgets had focus too. It's important in this case to use the 4th parameter of [[addEventHandler]] if you are only registered for the events of a child widget (cf. Example)
	*When a window is hidden with [[Dgs/DgsDxGUISetVisible\|dgsDxGUISetVisible]], it (or its child widget having focus) keeps focus internally until an other window gains focus or the chatbox is used		*When a window is hidden with [[Dgs/DgsDxGUISetVisible\|dgsDxGUISetVisible]], it (or its child widget having focus) keeps focus internally until an other window gains focus or the chatbox is used

Thisdp: /* Notes */

2017-06-25T09:21:29Z

Notes

← Older revision		Revision as of 09:21, 25 June 2017
Line 46:		Line 46:
	*When the focus is transfered from one DGS element to an other, it is guaranteed that ''onClientDgsDxBlur'' on the element that lost focus is triggered before [[onClientDgsDxBlur]] on the element that just gained focus		*When the focus is transfered from one DGS element to an other, it is guaranteed that ''onClientDgsDxBlur'' on the element that lost focus is triggered before [[onClientDgsDxBlur]] on the element that just gained focus
	*When the focus of a full window is lost (transfered to an other window or lost), ''onClientDgsDxBlur'' is only triggered for the window itself even if one of its widgets had focus too. It's important in this case to use the 4th parameter of [[addEventHandler]] if you are only registered for the events of a child widget (cf. Example)		*When the focus of a full window is lost (transfered to an other window or lost), ''onClientDgsDxBlur'' is only triggered for the window itself even if one of its widgets had focus too. It's important in this case to use the 4th parameter of [[addEventHandler]] if you are only registered for the events of a child widget (cf. Example)
	*When a window is hidden with [[Dgs/DgsDxGUISetVisible]], it (or its child widget having focus) keeps focus internally until an other window gains focus or the chatbox is used		*When a window is hidden with [[Dgs/DgsDxGUISetVisible\|dgsDxGUISetVisible]], it (or its child widget having focus) keeps focus internally until an other window gains focus or the chatbox is used

	==See Also==		==See Also==

Thisdp: /* Notes */

2017-06-25T09:20:59Z

Notes

← Older revision		Revision as of 09:20, 25 June 2017
Line 46:		Line 46:
	*When the focus is transfered from one DGS element to an other, it is guaranteed that ''onClientDgsDxBlur'' on the element that lost focus is triggered before [[onClientDgsDxBlur]] on the element that just gained focus		*When the focus is transfered from one DGS element to an other, it is guaranteed that ''onClientDgsDxBlur'' on the element that lost focus is triggered before [[onClientDgsDxBlur]] on the element that just gained focus
	*When the focus of a full window is lost (transfered to an other window or lost), ''onClientDgsDxBlur'' is only triggered for the window itself even if one of its widgets had focus too. It's important in this case to use the 4th parameter of [[addEventHandler]] if you are only registered for the events of a child widget (cf. Example)		*When the focus of a full window is lost (transfered to an other window or lost), ''onClientDgsDxBlur'' is only triggered for the window itself even if one of its widgets had focus too. It's important in this case to use the 4th parameter of [[addEventHandler]] if you are only registered for the events of a child widget (cf. Example)
	*When a window is hidden with [[~~dgsDxGUISetVisible~~]], it (or its child widget having focus) keeps focus internally until an other window gains focus or the chatbox is used		*When a window is hidden with [[Dgs/DgsDxGUISetVisible]], it (or its child widget having focus) keeps focus internally until an other window gains focus or the chatbox is used

	==See Also==		==See Also==