View Single Post
04/28/15, 08:44 AM   #11
votan
 
votan's Avatar
AddOn Author - Click to view addons
Join Date: Oct 2014
Posts: 577
Originally Posted by Kevinmon View Post
I have this same bug every time I play.
This is, what you have to care of:
Once you open a context-menu the first time after (re-)load UI, remember the position of the first menu entry introduced by an add-on. Build-in menu enties using a "private" function at the same position will raise this "security feature" error message afterwards.
Typically "private" functions are in the position 1 to 3, sometimes 4 of the inventory context-menu. Once this positions were created by build-in menu entries first, the message will not occur anymore.
If, for example, the build-in context-menu normally has 2 menu entries only and an addon introduces a 3rd menu item first time ever after load, a "private" build-in menu item at position 3 will crash.

If you have that error so frequently, what context-menu do you normally use first very often?

Edit 1: I have to correct myself. I finally found a way to get an "insecure" 4th menu item, but it worked. But I'm still able to reproduce the error, if the 1st menu item was created by a full custom context-menu.
So it must have something to do with the first initialization.

Last edited by votan : 04/28/15 at 12:45 PM.
  Reply With Quote