Fix addon initialization order with guard checks

Refactor mouseover extensions to split initialization into two phases: OnLoad (empty) and OnAddOnLoad (actual setup). This ensures hooks are only registered when the target addon's globals are defined. Add guard clauses to check for required functions before hooking. Also remove Cursive's premature initialization attempt.
This commit is contained in:
Brues
2026-07-27 14:32:12 -05:00
parent 586c51b53a
commit 9bebbbb836
8 changed files with 33 additions and 19 deletions
+4 -2
View File
@@ -23,7 +23,9 @@ function Extension.SetHook(widget)
end)
end
function Extension.OnLoad()
function Extension.OnLoad() end
function Extension.OnAddOnLoad()
if not CT_AssistFrame then
return
end
@@ -35,4 +37,4 @@ function Extension.OnLoad()
Extension.SetHook(CT_AssistFrame_Drag)
end
EventUtil.ContinueOnAddOnLoaded("CT_UnitFrames", Extension.OnLoad)
EventUtil.ContinueOnAddOnLoaded("CT_UnitFrames", Extension.OnAddOnLoad)