Originally Posted by merlight
I like your pool hack more  This would be adding another UI element, and I can already see myself hovering over an item and thinking: "Is the thing I want to do in the core menu or an add-on?"
The whole menu interface looks very... old... like from before there was a class for ZO_Anything.
How about passing an optional object pool key to AddMenuItem?
Lua Code:
function AddMenuItem(mytext, myfunction, itemType, myfont, normalColor, highlightColor, itemYPad, itemKey) local menuItemControl = ZO_Menu.itemPool:AcquireObject(itemKey)
You can use a string key with add-on name + some suffix, AcquireObject will create one object for that key and always return that one. That way you won't "steal" a secure menu item. Don't know if we can hook AddMenuItem and not break everything, in which case this parameter would've to be added by ZOS. |
Hehe, thanks.
Well, we can not hook AddMenuItem, as it would make all code paths "in-secure". So, build-in menu entries must look as they do now.
I will try some things at weekend.
Back to QuadroTony's error:
Does it happen, if MM is not active, too?