WoW:BagId - Revision history

Move page script: Move page script moved page BagId to WoW:BagId without leaving a redirect

2023-08-15T04:47:51Z

Move page script moved page BagId to BagId without leaving a redirect

← Older revision

Revision as of 04:47, 15 August 2023

Bear at 03:46, 30 October 2013

2013-10-30T03:46:24Z

← Older revision		Revision as of 03:46, 30 October 2013
Line 1:		Line 1:
	{{wowapitype}}~~<br>~~		{{wowapitype}}

	While dealing with container and inventory items, many developers use a bag/slot couple and set bag to -1 for the case of an inventory item. But a problem occurs when the bank is opened (after BANKFRAME_OPENED event being fired) because the 28 slots of the bank count as actual container slots with -1 as bagID. In the same idea, items in the bank bags can be accessed via container item functions (like [[API GetContainerItemLink\|GetContainerItemLink(bagID, slotID)]], [[API PickupContainerItem\|PickupContainerItem(bagID, slotID)]]) with 5 as bagID for the first bank bag, 6 for the second ... until 11 for the seventh.		While dealing with container and inventory items, many developers use a bag/slot couple and set bag to -1 for the case of an inventory item. But a problem occurs when the bank is opened (after BANKFRAME_OPENED event being fired) because the 28 slots of the bank count as actual container slots with -1 as bagID. In the same idea, items in the bank bags can be accessed via container item functions (like [[API GetContainerItemLink\|GetContainerItemLink(bagID, slotID)]], [[API PickupContainerItem\|PickupContainerItem(bagID, slotID)]]) with 5 as bagID for the first bank bag, 6 for the second ... until 11 for the seventh.

Line 27:		Line 26:
	* NUM_BAG_SLOTS+1 to NUM_BAG_SLOTS+NUM_BANKBAGSLOTS are your bank bags		* NUM_BAG_SLOTS+1 to NUM_BAG_SLOTS+NUM_BANKBAGSLOTS are your bank bags

	This follows the way [[FrameXML]] works. Future changes to APIs are less likely to make your addon break if you follow it. Many of these globals are defined in FrameXML\Constants.lua, if you're curious.		This follows the way [[FrameXML]] works. Future changes to APIs are less likely to make your addon break if you follow it. Many of these globals are defined in FrameXML\Constants.lua, if you're curious.

WoWWiki>Farmbuyer at 07:48, 14 October 2010

2010-10-14T07:48:11Z

← Older revision		Revision as of 07:48, 14 October 2010
Line 20:		Line 20:

	* 0 is your backpack		* 0 is your backpack
	* 1 to NUM_BAG_SLOTS are your bags ~~(NUM_BAG_SLOTS defined in FrameXML\BankFrame.lua, line 2)~~		* 1 to NUM_BAG_SLOTS are your bags
	* KEYRING_CONTAINER is the keyring		* KEYRING_CONTAINER is the keyring

Line 27:		Line 27:
	* NUM_BAG_SLOTS+1 to NUM_BAG_SLOTS+NUM_BANKBAGSLOTS are your bank bags		* NUM_BAG_SLOTS+1 to NUM_BAG_SLOTS+NUM_BANKBAGSLOTS are your bank bags

	This follows the way [[FrameXML]] works. Future changes to APIs are less likely to make your addon break if you follow it.		This follows the way [[FrameXML]] works. Future changes to APIs are less likely to make your addon break if you follow it. Many of these globals are defined in FrameXML\Constants.lua, if you're curious.

WoWWiki>Evilfox: added tokens bag info

2009-10-23T22:04:56Z

added tokens bag info

← Older revision		Revision as of 22:04, 23 October 2009
Line 8:		Line 8:
	* 1 to 4 for the bags on the character (numbered right to left)		* 1 to 4 for the bags on the character (numbered right to left)
	* -2 for the keyring		* -2 for the keyring
			* -4 for the tokens bag

	While the bank is opened:		While the bank is opened:

WoWWiki>Charibot: catfix, Replaced: {{wowapitype}} → {{wowapitype}}

2008-07-15T00:56:51Z

catfix, Replaced: {{wowapitype}} → {{wowapitype}}<br>

← Older revision		Revision as of 00:56, 15 July 2008
Line 1:		Line 1:
	{{wowapitype}}		{{wowapitype}}<br>

	While dealing with container and inventory items, many developers use a bag/slot couple and set bag to -1 for the case of an inventory item. But a problem occurs when the bank is opened (after BANKFRAME_OPENED event being fired) because the 28 slots of the bank count as actual container slots with -1 as bagID. In the same idea, items in the bank bags can be accessed via container item functions (like [[API GetContainerItemLink\|GetContainerItemLink(bagID, slotID)]], [[API PickupContainerItem\|PickupContainerItem(bagID, slotID)]]) with 5 as bagID for the first bank bag, 6 for the second ... until 11 for the seventh.		While dealing with container and inventory items, many developers use a bag/slot couple and set bag to -1 for the case of an inventory item. But a problem occurs when the bank is opened (after BANKFRAME_OPENED event being fired) because the 28 slots of the bank count as actual container slots with -1 as bagID. In the same idea, items in the bank bags can be accessed via container item functions (like [[API GetContainerItemLink\|GetContainerItemLink(bagID, slotID)]], [[API PickupContainerItem\|PickupContainerItem(bagID, slotID)]]) with 5 as bagID for the first bank bag, 6 for the second ... until 11 for the seventh.

WoWWiki>Psychogears: /* How you should code */

2008-05-17T03:10:50Z

How you should code

← Older revision		Revision as of 03:10, 17 May 2008
Line 19:		Line 19:

	* 0 is your backpack		* 0 is your backpack
	* 1 -- NUM_BAG_SLOTS are your bags		* 1 to NUM_BAG_SLOTS are your bags (NUM_BAG_SLOTS defined in FrameXML\BankFrame.lua, line 2)
	* KEYRING_CONTAINER is the keyring		* KEYRING_CONTAINER is the keyring

	While the bank is opened:		While the bank is opened:
	* BANK_CONTAINER is the bank window		* BANK_CONTAINER is the bank window
	* NUM_BAG_SLOTS+1 -- NUM_BAG_SLOTS+NUM_BANKBAGSLOTS are your bank bags		* NUM_BAG_SLOTS+1 to NUM_BAG_SLOTS+NUM_BANKBAGSLOTS are your bank bags

	This follows the way [[FrameXML]] works. Future changes to APIs are less likely to make your addon break if you follow it.		This follows the way [[FrameXML]] works. Future changes to APIs are less likely to make your addon break if you follow it.

WoWWiki>Mikk: Make 2.0 changes seem less new. Document constant names and how you SHOULD code.

2007-05-28T11:55:35Z

Make 2.0 changes seem less new. Document constant names and how you SHOULD code.

← Older revision		Revision as of 11:55, 28 May 2007
Line 1:		Line 1:
	{{wowapitype}}		{{wowapitype}}

	~~<center>''Documentation by [[user:Ebnusn\|Ebnusn]]''</center>~~		While dealing with container and inventory items, many developers use a bag/slot couple and set bag to -1 for the case of an inventory item. But a problem occurs when the bank is opened (after BANKFRAME_OPENED event being fired) because the 28 slots of the bank count as actual container slots with -1 as bagID. In the same idea, items in the bank bags can be accessed via container item functions (like [[API GetContainerItemLink\|GetContainerItemLink(bagID, slotID)]], [[API PickupContainerItem\|PickupContainerItem(bagID, slotID)]]) with 5 as bagID for the first bank bag, 6 for the second ... until 11 for the seventh.
	~~----~~
	While dealing with container and inventory items, many developers use a bag/slot couple and set bag to -1 for the case of an inventory item. But a problem occurs when the bank is opened (after BANKFRAME_OPENED event being fired) because the ~~24 (~~28 ~~after v2.0)~~ slots of the bank count as a container with -1 as bagID. In the same idea, items in the bank bags can be accessed via container item functions (like [[API GetContainerItemLink\|GetContainerItemLink(bagID, slotID)]], [[API PickupContainerItem\|PickupContainerItem(bagID, slotID)]]) with 5 as bagID for the first bank bag, 6 for the second ... until 10 for the ~~sixth~~.

	To sum up, the possibilities for bagID are :		To sum up, the current possibilities for bagID are :

	: 0 for the backpack		* 0 for the backpack
	: 1 to 4 for the bags on the character (numbered right to left)		* 1 to 4 for the bags on the character (numbered right to left)
	: -2 for the keyring		* -2 for the keyring
	~~WHILE THE BANK IS OPENED~~ :
	: -1 for the bank content		While the bank is opened:
	: 5 to 10 for bank bags (numbered left to right)		* -1 for the bank content
	: ~~11 for~~ the ~~additional~~ bank ~~slot created in interface release 2~~.0		* 5 to 11 for bank bags (numbered left to right, was 5-10 prior to 2.0)


			== How you should code ==

			You should not assume fixed numbers when there are named constants to use. Access your bags according to the following scheme:

			* 0 is your backpack
			* 1 -- NUM_BAG_SLOTS are your bags
			* KEYRING_CONTAINER is the keyring

			While the bank is opened:
			* BANK_CONTAINER is the bank window
			* NUM_BAG_SLOTS+1 -- NUM_BAG_SLOTS+NUM_BANKBAGSLOTS are your bank bags

			This follows the way [[FrameXML]] works. Future changes to APIs are less likely to make your addon break if you follow it.

WoWWiki>Farmbuyer at 06:33, 11 April 2007

2007-04-11T06:33:44Z

← Older revision		Revision as of 06:33, 11 April 2007
Line 3:		Line 3:
	<center>''Documentation by [[user:Ebnusn\|Ebnusn]]''</center>		<center>''Documentation by [[user:Ebnusn\|Ebnusn]]''</center>
	----		----
	While dealing with container and inventory items, many developers use a bag/slot couple and set bag to -1 for the case of an inventory item. But a problem occurs when the bank is opened (after BANKFRAME_OPENED event being fired) because the 24 slots of the bank count as a container with -1 as bagID. In the same idea, items in the bank bags can be accessed via container item functions (like [[API GetContainerItemLink\|GetContainerItemLink(bagID, slotID)]], [[API PickupContainerItem\|PickupContainerItem(bagID, slotID)]]) with 5 as bagID for the first bank bag, 6 for the second ... until 10 for the sixth.		While dealing with container and inventory items, many developers use a bag/slot couple and set bag to -1 for the case of an inventory item. But a problem occurs when the bank is opened (after BANKFRAME_OPENED event being fired) because the 24 (28 after v2.0) slots of the bank count as a container with -1 as bagID. In the same idea, items in the bank bags can be accessed via container item functions (like [[API GetContainerItemLink\|GetContainerItemLink(bagID, slotID)]], [[API PickupContainerItem\|PickupContainerItem(bagID, slotID)]]) with 5 as bagID for the first bank bag, 6 for the second ... until 10 for the sixth.

	To sum up, the possibilities for bagID are :		To sum up, the possibilities for bagID are :

WoWWiki>Rozak: Added bagid 11 for new bank slot

2006-12-12T12:21:44Z

Added bagid 11 for new bank slot

← Older revision		Revision as of 12:21, 12 December 2006
Line 13:		Line 13:
	: -1 for the bank content		: -1 for the bank content
	: 5 to 10 for bank bags (numbered left to right)		: 5 to 10 for bank bags (numbered left to right)
			: 11 for the additional bank slot created in interface release 2.0

WoWWiki>BCheck: info for patch 1.11

2006-06-20T19:10:32Z

info for patch 1.11

← Older revision		Revision as of 19:10, 20 June 2006
Line 9:		Line 9:
	: 0 for the backpack		: 0 for the backpack
	: 1 to 4 for the bags on the character (numbered right to left)		: 1 to 4 for the bags on the character (numbered right to left)
			: -2 for the keyring
	WHILE THE BANK IS OPENED :		WHILE THE BANK IS OPENED :
	: -1 for the bank content		: -1 for the bank content
	: 5 to 10 for bank bags (numbered left to right)		: 5 to 10 for bank bags (numbered left to right)