Originally Posted by QuadroTony
votan's settings menu told its LibCustomMenu Rev. 1
|
Yep, that's the newest and only existing version.
Just clarify for those new to this topic:
LibCustomMenu is not an automatic fix. It can't be, because of the "secure" checks:
Any add-on code is "in-secure". Therefore LibCustomMenu can not prevent other add-ons from calling AddMenuItem by hooking it. Because that would make "secure" code "in-secure", too.
Instead LibCustomMenu introduces a new global function AddCustomMenuItem, which should be used by all add-ons calling AddMenuItem.
This function swaps the control-pools before calling AddMenuItem itself and swaps back again. This way the "secure" code does not re-use "in-secure" controls simply because the pools do not contain them.
But if ZOS has extend the "secure" check, this work-around may not work anymore...
BTW: This technique could be used to introduce new menu-item-types, if it is still allowed.