Annoying Pop-up Remover

Annoying Pop-up Remover

215k Downloads

Equip or use a Refundable item do not work on draenor plans

edu5ardo opened this issue ยท 3 comments

commented

When I want to learn a building plan for Draenor Fortress, it is not possible, I must deactivate "Equip or use a Refundable item" for use it

commented

Apparently Blizzard has made the function ConfirmNoRefundOnUse() protected. Not sure if this was an intended change or not. I might have to turn off APR's attempts to hide that dialog until it gets sorted out.

Diagnostic info for my reference:

1x [ADDON_ACTION_FORBIDDEN] AddOn 'AnnoyingPopupRemover' tried to call the protected function 'ConfirmNoRefundOnUse()'.
[string "@!BugGrabber/BugGrabber.lua"]:485: in function <!BugGrabber/BugGrabber.lua:485>
[string "=[C]"]: in function `ConfirmNoRefundOnUse'
[string "@Blizzard_StaticPopup_Frame/Mainline/StaticPopup.lua"]:1888: in function `OnAccept'
[string "@AnnoyingPopupRemover/module_equip_refund.lua"]:155: in function `?'
[string "@AnnoyingPopupRemover/AnnoyingPopupRemover.lua"]:453: in function <AnnoyingPopupRemover/AnnoyingPopupRemover.lua:452>
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: in function `UseContainerItem'
[string "@Blizzard_UIPanels_Game/Mainline/ContainerFrame.lua"]:1442: in function <...s/Blizzard_UIPanels_Game/Mainline/ContainerFrame.lua:1336>
[string "=[C]"]: in function `ContainerFrameItemButton_OnClick'
[string "@Blizzard_UIPanels_Game/Mainline/ContainerFrame.lua"]:1502: in function <...s/Blizzard_UIPanels_Game/Mainline/ContainerFrame.lua:1489>
[string "=[C]"]: ?

Locals:
_ = Frame {
}
event = "ADDON_ACTION_FORBIDDEN"
events = <table> {
}
commented

I disabled the code that APR uses to bypass that dialog in commit bf6e438; it will be in v23.4.0. When and if Blizz ever restores the ability for addons to use that protected function, I can re=enable this feature. I'll keep this open to remind me to check periodically, but sadly this is something I can't fix from my side.

commented

Blizzard reverted their change, and I reverted mine. :) This is back to normal in v23.9.0-release.