View Bug Report | ||||||||||||||
|
Notes | Sort Options |
By: CodeStripper - 07/06/22 08:12 PM |
Heyo, I'd like to include some more information on this and a possible solution: 1. The bug will only occur once the "HandleSlotChanged" function is called after the initial call. I noticed that this function calls the base esoui function "SetupItemSlot" when an item is populated in one of the quickslots. This function in turn calls "SetupActionSlotWithBg" then "SetupActionSlot" which enables the button. 2. If the quick slot is empty, it runs the "SetupEmptyActionSlot" function which does nothing, so anything that contains a quick slotted item past the variable defined in the addon settings (default 4) will have it's button UI re-enabled after a HandleSlotChanged function call occurs for that item slot. The Fix: In -> "QuickButtons.lua" Functions -> "AUI.Actionbar.QuickButtons.UpdateCooldowns" "AUI.Actionbar.QuickButtons.OnFullUpdate" "AUI.Actionbar.QuickButtons.OnSlotUpdate" Add in a check to make sure the quick slot is active before calling "HandleSlotChanged" like the following: Code:
for slotId, quickButton in pairs(gQuickButtonArray) do if IsQuickSlotActive(slotId) then quickButton:HandleSlotChanged(HOTBAR_CATEGORY_QUICKSLOT_WHEEL) end end |