[ADDON_ACTION_BLOCKED] tried to call the protected function "<unnamed>:SetHeight()".
Hi all,
I am currently making an addon that displays all the enemies' unitframe by reproducing nameplates based on NAME_PLATE_CREATED, NAME_PLATE_UNIT_ADDED, NAME_PLATE_UNIT_REMOVED events. Lua Code:
I am aware of that this taint is occurring because the new nameplates are being created and the height is set while in the combat. + The reason that I am using SecureHandlerStateTemplate is to hide such frame while in a pet battle (as it is shown in L#40). Is there any possible solution to prevent such taint occurring? Or should I only use my handler only to hide/show the frame in/out of pet battle, and create another frame on top of it which manages visual part? Thank you! |
You really don't want to use secure templates for your nameplates, speaking from experience.
Moreover, aren't nameplates hidden while pet battling anyway? Why are you trying to do that manually? O_o |
Quote:
First of all, it was a bad word choice of me :( What I meant was that I am trying to create a list of unitframes which works like nameplates, but instead of hovering above the unit they will be lined up at a certain position. Something like this: I've made some modifications after posting this thread and now there are basically two templates being used. Lua Code:
One is SecureHandlerStateTemplate for handler object to hide/show frames when the player is in/out of the pet battle as I stated before and the other is SecureUnitButtonTemplate for each nameplates that are being created to give some functionalities like mouseover cast, etc. The errors that I'm getting are: Lua Code:
Lua Code:
mmmmmmmmmmmmmmmmm................ Secure templates are so complicated!!!!! |
Aight, just decided change the structure.
Instead of nameplates being created on NAME_PLATE_CREATED, I decided to create certain amount of nameplates on ADDON_LOADED which will no longer cry for Lua Code:
this error. So, the current concern is Lua Code:
Seriously... what are they? I thought it was crying because it doesn't have an assigned OnClick script and so I actually gave an empty OnClick script Lua Code:
then it starts to toss me the following. Lua Code:
I've been searching for the solution on google and the only result that I got was from those Z-perl (or X-perl) users reporting such issue and I couldn't really find the answer :confused: |
What frames have the name FrameName in it ? None of the code you have supplied includes frames with that naming.
The error message itself sounds like it is being caused by an xml file as no line numbers are being reported. If you have other addons activated, try just your addon and see if those errors still occur. |
Quote:
They are the frames (nameplates) that I create on NAME_PLATE_CREATED event as shown in L#16 of my first reply. Quote:
The error persists only when the BugGrabber addon is on :confused: What am I missing...? I mean I am a big fan(?) of oUF and afaik oUF also uses SecureUnitButtonTemplate which it doesn't report such error even if the BugGrabber addon is turned on...... mmmmmmmmmmmmmmmmmmmmmmmm.................. |
Ah... I think I found why...
The object type for my nameplate frame was a Frame rather than a Button.... After changing the type to Button, it stopped crying for that OnClick issue. Now the next step would be giving some functionalities like mouseover cast and etc ;) |
So you're trying to make your own enemy grid, eh? Don't get your hopes up though, there's a reason why that addon is pretty much dead nowadays.
And yes, frames don't have onclick scripts, good that you figured it out yourself. |
Quote:
But why is it so? Is that because of the same reason? Blizzard blocked some sort of functionality cause the idea was way too powerful? |
Quote:
Google "enemy grid nerf". It's a fun read :P |
Quote:
|
All times are GMT -6. The time now is 11:04 PM. |
vBulletin © 2024, Jelsoft Enterprises Ltd
© 2004 - 2022 MMOUI