Content
|
|
|
|
Stats
|
|
Files: 15
Downloads: 326,371
Favorites:
|
|
New & Updated
|
|
|
WOWInterface
|
|
|
|
|
|
View Bug Report
|
| SetAttribute Bug 3.0 |
| Bug #: |
5048 |
| File: |
oUF |
| Date: |
10-29-2008 03:55 AM |
| By: |
Blood Druid |
| Status: |
Game Bug (Cant fix)
|
With last version of a patch began to receive an error:
"Interface \\FrameXML \\SecureHandlers.lua:511: Cannot use SecureHandlers API during combat"
the Error arises only then when I am in combat and during this moment occurs invate in group or raid
Here that contains in this function in SecureHandlers.lua:
Code:
local function API_OnAttributeChanged (self, name, value)
if (value == nil) then
return;
end
if (InCombatLockdown ()) then
- This should not ever happen because API frame is protected,
- but just in case someone does something silly...
error ("Cannot use SecureHandlers API during combat");
return;
end
.........
end
It turns out already it is impossible to use SetAttribute... Haste, please, make that be with it
P.S. I am sorry for wrong formulations, I use the automatic translator on English |
|
 Notes |
| By: dutorien - 10-31-2008 09:18 AM |
I have exactly the same problem
Duto
|
| By: haste - 11-01-2008 10:07 AM |
|
It's a blizzard bug, sadly enough.
|
| By: zork - 11-27-2008 09:51 AM |
|
Can we do anything against this behavior? Sth. that will not generate the lua error and hinders the party frame from spawning?
|
| By: p3lim - 12-25-2008 06:28 PM |
|
Haste, to fix this error, make a CombatLockdown check on attribute changes, and force them to change once combat is dropped.
|
| By: p3lim - 12-27-2008 01:59 AM |
Its most likely intended, not a bug. Changing attributes in combat is protected, thats why this error is popping up.
So you cant ignore this
|
|
