WoW:API SetWhoToUI - Revision history

Move page script: Move page script moved page API SetWhoToUI to WoW:API SetWhoToUI without leaving a redirect

2023-08-15T04:47:24Z

Move page script moved page API SetWhoToUI to API SetWhoToUI without leaving a redirect

← Older revision

Revision as of 04:47, 15 August 2023

WoWWiki>Fandyllic: move comment to talk page

2008-05-08T23:45:48Z

move comment to talk page

← Older revision		Revision as of 23:45, 8 May 2008
Line 30:		Line 30:

	:'''Note - Hooking FriendsFrame's OnEvent handler is a really bad idea''', because FriendsFrame contains the raid tab. This would likely cause you a lot of problems with the new secure framework. Using FriendsFrame:Hide() is also probably not a good idea unless you're absolutely sure when your code is going to be run. Otherwise, you may inadvertantly hide the FriendsFrame when the player is using it.		:'''Note - Hooking FriendsFrame's OnEvent handler is a really bad idea''', because FriendsFrame contains the raid tab. This would likely cause you a lot of problems with the new secure framework. Using FriendsFrame:Hide() is also probably not a good idea unless you're absolutely sure when your code is going to be run. Otherwise, you may inadvertantly hide the FriendsFrame when the player is using it.

	:'''I agree with the above.''' I hooked the ''WhoList_Update'' function instead. This is the function called by the event handler as well as other parts of the code that brings up the FriendsFrame in Who mode. My code is below

	~~OrigWhoList_Update = WhoList_Update;~~
	~~function WhoList_Update()~~
	~~if (not SWALLOW_NEXT_WHO) then~~
	~~OrigWhoList_Update();~~
	~~end~~
	~~end~~

	~~- [[User:Hillie\|Hillie]] ([[User talk:Hillie\|talk]]) 21:54, 8 May 2008 (UTC)~~

WoWWiki>Hillie: /* Notes */ some formatting, and code changes to accomodate those who will copy/paste and want the code to work

2008-05-08T21:54:32Z

Notes: some formatting, and code changes to accomodate those who will copy/paste and want the code to work

← Older revision		Revision as of 21:54, 8 May 2008
Line 30:		Line 30:

	:'''Note - Hooking FriendsFrame's OnEvent handler is a really bad idea''', because FriendsFrame contains the raid tab. This would likely cause you a lot of problems with the new secure framework. Using FriendsFrame:Hide() is also probably not a good idea unless you're absolutely sure when your code is going to be run. Otherwise, you may inadvertantly hide the FriendsFrame when the player is using it.		:'''Note - Hooking FriendsFrame's OnEvent handler is a really bad idea''', because FriendsFrame contains the raid tab. This would likely cause you a lot of problems with the new secure framework. Using FriendsFrame:Hide() is also probably not a good idea unless you're absolutely sure when your code is going to be run. Otherwise, you may inadvertantly hide the FriendsFrame when the player is using it.

			:'''I agree with the above.''' I hooked the ''WhoList_Update'' function instead. This is the function called by the event handler as well as other parts of the code that brings up the FriendsFrame in Who mode. My code is below

			OrigWhoList_Update = WhoList_Update;
			function WhoList_Update()
			if (not SWALLOW_NEXT_WHO) then
			OrigWhoList_Update();
			end
			end

			- [[User:Hillie\|Hillie]] ([[User talk:Hillie\|talk]]) 21:54, 8 May 2008 (UTC)

WoWWiki>Progdog: /* Notes */

2006-12-18T23:22:45Z

Notes

← Older revision		Revision as of 23:22, 18 December 2006
Line 28:		Line 28:

	:Of course your code should make sure to reset <tt>iAmWaitinForAReply</tt> periodically (e.g. in case you never get a reply!), and you should probably read [[HOWTO:_Hook_a_Function]] for more info on that subject.		:Of course your code should make sure to reset <tt>iAmWaitinForAReply</tt> periodically (e.g. in case you never get a reply!), and you should probably read [[HOWTO:_Hook_a_Function]] for more info on that subject.

			:'''Note - Hooking FriendsFrame's OnEvent handler is a really bad idea''', because FriendsFrame contains the raid tab. This would likely cause you a lot of problems with the new secure framework. Using FriendsFrame:Hide() is also probably not a good idea unless you're absolutely sure when your code is going to be run. Otherwise, you may inadvertantly hide the FriendsFrame when the player is using it.

WoWWiki>Groklam at 14:27, 21 August 2006

2006-08-21T14:27:31Z

← Older revision		Revision as of 14:27, 21 August 2006
Line 1:		Line 1:
	~~<center>'''SetWhoToUI''' - ''Documentation by~~ [[~~User:Noccy\|Noccy~~]]~~''</center>~~		{{wowapi}} __NOTOC__

			Sets where the result of a [[API SendWho]] request will be handled.

	SetWhoToUI(state);		SetWhoToUI(state);

	~~:Sets where the result of a [[API SendWho]] request will be handled.~~

	== Parameters ==		== Parameters ==
Line 14:		Line 14:

	=== Notes ===		=== Notes ===
	:During my experiments with this function, the Who dialog still popped up. However, this can be avoided by using FriendsFrame:Hide(); or a combination of FriendsFrame:UnregisterEvent("WHO_LIST_UPDATE"); and FriendsFrame:RegisterEvent("WHO_LIST_UPDATE");		:During [[User:Noccy\|my]] experiments with this function, the Who dialog still popped up. However, this can be avoided by using FriendsFrame:Hide(); or a combination of FriendsFrame:UnregisterEvent("WHO_LIST_UPDATE"); and FriendsFrame:RegisterEvent("WHO_LIST_UPDATE");

			:Another way (perhaps slightly less complex, and easier to get to work with other addons) of avoiding the Who window popping up is to hook the <tt>FriendsFrame_OnEvent</tt> function and not letting the original handle <tt>WHO_LIST_UPDATE</tt> events when your own code is waiting for a reply. ''Example:''

			function my_FriendsFrame_OnEvent()
			if not(event == "WHO_LIST_UPDATE" and iAmWaitingForAReply) then
			original_FriendsFrame_OnEvent();
			end
			end

			original_FriendsFrame_OnEvent = FriendsFrame_OnEvent;
			FriendsFrame_OnEvent = my_FriendsFrame_OnEvent;

	~~__NOTOC__~~		:Of course your code should make sure to reset <tt>iAmWaitinForAReply</tt> periodically (e.g. in case you never get a reply!), and you should probably read [[HOWTO:_Hook_a_Function]] for more info on that subject.
	~~{{Template~~:~~WoW API}}~~

WoWWiki>Kevinoid: Added note to unregister event from FriendsFrame

2006-01-14T04:27:07Z

Added note to unregister event from FriendsFrame

← Older revision		Revision as of 04:27, 14 January 2006
Line 14:		Line 14:

	=== Notes ===		=== Notes ===
	:During my experiments with this function, the Who dialog still popped up. However, this can be avoided by using FriendsFrame:Hide();		:During my experiments with this function, the Who dialog still popped up. However, this can be avoided by using FriendsFrame:Hide(); or a combination of FriendsFrame:UnregisterEvent("WHO_LIST_UPDATE"); and FriendsFrame:RegisterEvent("WHO_LIST_UPDATE");

	__NOTOC__		__NOTOC__
	{{Template:WoW API}}		{{Template:WoW API}}

WoWWiki>Noccy: /* Arguments */ - Changed string to number. Must have been tired as i wrote it the first time ;)

2005-11-06T16:55:51Z

Arguments: - Changed string to number. Must have been tired as i wrote it the first time ;)

New page

<center>'''SetWhoToUI''' - ''Documentation by [[User:Noccy|Noccy]]''</center>

SetWhoToUI(state);

:Sets where the result of a [[API SendWho]] request will be handled.

== Parameters ==
=== Arguments ===
:(State)
:;State : Number - If set to 1, the result of a SendWho will always be returned as a WHO_LIST_UPDATE event. If set to 0 then the result of a SendWho will be returned as a CHAT_MSG_SYSTEM if the list is short, but as a WHO_LIST_UPDATE if the list is long. (from WoW forums)

=== Returns ===
:Nothing.

=== Notes ===
:During my experiments with this function, the Who dialog still popped up. However, this can be avoided by using FriendsFrame:Hide();

__NOTOC__
{{Template:WoW API}}