yesterday, while looking for options to optimize my ui's performance, i found the blizzard-combatlog-window. i never use that, and it is processing a huge number of events in raid-combat, so i thought hey, why not disable it completely. so what i did was create a new autoexec script with the following code:
Code:
COMBATLOG:SetScript("OnUpdate", nil)
COMBATLOG:SetScript("OnEvent", nil)
COMBATLOG:SetScript("OnShow", nil)
COMBATLOG:SetScript("OnHide", nil)
CombatLogUpdateFrame:SetScript("OnUpdate", nil)
COMBATLOG:UnregisterAllEvents()
CombatLogUpdateFrame:UnregisterAllEvents()
this does work, and the combatlog window now processes no events at all
now, i added this to an autoexec script, reloged, and my complete ui was gone, no rdx frames at all. since it worked when i manually called that script after the ui was fully loaded, i delayed it a bit in the autoexec script (moved the code to a function and called that via VFL.ZMSchedule with a delay of 0.1) and after that rdx loads as expected.
now the question is: why does it kill rdx if i call that script in an autoexec with no delay? how does rdx use the blizzard combatlog window so that it does not load without it ?
Threaded Mode
