__NOWYSIWYG__ {| class="darktable" |- ! style="position:relative" | Reference e |- | AddOns WoW API Widget API XML UI Event API WoW Lua Macro API CVars Changes |} → [[:Category:|]] [[Category:]]__NOWYSIWYG__ru:Шаблон:WoWAPI __TOC__← [[|]] 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 GetContainerItemLink(bagID, slotID), PickupContainerItem(bagID, slotID)) with 5 as bagID for the first bank bag, 6 for the second ... until 11 fo
| Attributes | Values |
|---|
| rdfs:label
| |
| rdfs:comment
| - __NOWYSIWYG__ {| class="darktable" |- ! style="position:relative" | Reference e |- | AddOns WoW API Widget API XML UI Event API WoW Lua Macro API CVars Changes |} → [[:Category:|]] [[Category:]]__NOWYSIWYG__ru:Шаблон:WoWAPI __TOC__← [[|]] 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 GetContainerItemLink(bagID, slotID), PickupContainerItem(bagID, slotID)) with 5 as bagID for the first bank bag, 6 for the second ... until 11 fo
|
| dbkwik:wowwiki/pro...iPageUsesTemplate
| |
| abstract
| - __NOWYSIWYG__ {| class="darktable" |- ! style="position:relative" | Reference e |- | AddOns WoW API Widget API XML UI Event API WoW Lua Macro API CVars Changes |} → [[:Category:|]] [[Category:]]__NOWYSIWYG__ru:Шаблон:WoWAPI __TOC__← [[|]] 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 GetContainerItemLink(bagID, slotID), PickupContainerItem(bagID, slotID)) with 5 as bagID for the first bank bag, 6 for the second ... until 11 for the seventh. To sum up, the current possibilities for bagID are :
* 0 for the backpack
* 1 to 4 for the bags on the character (numbered right to left)
* -2 for the keyring
* -4 for the tokens bag While the bank is opened:
* -1 for the bank content
* 5 to 11 for bank bags (numbered left to right, was 5-10 prior to 2.0)
|
![[RDF Data]](/fct/images/sw-rdf-blue.png)