X-Perl UnitFrames

1565 - XPerl_RaidFrames-r840\XPerl_Raid.lua:668: attempt to index local "self" (a number value)

What steps will reproduce the problem?
1. Leaving Combat
2.
3.

What is the expected output? What do you see instead?

What version of the product are you using?
3.6.30

Do you have an error log of what happened?

9x XPerl_RaidFrames-r840\XPerl_Raid.lua:668 attempt to index local "self" (a number value)
XPerl_RaidFrames-r840\XPerl_Raid.lua:668 in function <XPerl_RaidFrames\XPerl_Raid.lua:656
XPerl_RaidFrames-r840\XPerl_Raid.lua:1312 in function "func"
XPerl_RaidFrames-r840\XPerl_Raid.lua:1260 in function <XPerl_RaidFrames\XPerl_Raid.lua:1247

Locals:
self = XPerl_Raid_Frame {
0= <userdata>
 Array = <table> {}
 time = 0.081000003963709
}
(for generator) = <func> =[C]:-1
(for state) = <table> {
 2 = XPerl_Raid_Grp5UnitButton5 {}
}
(for control) = 2
frame = 2
arg = XPerl_Raid_Grp5UnitButton5 {
 0 = <userdata>
 highlight = XPerl_Raid_Grp5UnitButton5highlight {}
 nameFrame = XPerl_Raid_Grp5UnitButton5nameFrame {}
 lastName = "Tednuggets"
 lastID = "raid25"
 partyid = "raid25"
 edgeFile = "Addons\XPerl\images\XPerl_ThinEdge"
 statsFrame = XPerl_Raid_Grp5UnitButton5statsFrame {}
 edgeSize = 10
 voiceButton = XPerl_VoiceSpeaker {}
 PlayerFlash = false
 edgeInsets = 2
 FlashFrames = <table> {}
 buffFrame = XPerl_Raid_Grp5UnitButton5buffFrame {}
}
taintFrames = <table> {
 2 = XPerl_Raid_Grp5UnitButton5 {}
}
taintable = <func> @XPerl_RaidFrames\XPerl_Raid.lua:656

Please provide any additional information below.

User When Change
Asixandur Oct 31, 2013 at 05:46 UTC Changed status from Accepted to Declined
Asixandur May 13, 2013 at 13:36 UTC Changed assigned to from Zeksie to Tharai
Tharai Mar 27, 2013 at 04:15 UTC
CrimsonKMR Mar 19, 2013 at 22:26 UTC Create

You must login to post a comment. Don't have an account? Register to get one!

  • 3 comments
  • Avatar of only1yzerman only1yzerman Sep 28, 2013 at 01:22 UTC - 0 likes

    Didn't want to create a new bug for this, but as of the latest live version, this is still occurring. This error only seems to happen when I leave combat (die, stop attacking, target dies, etc).

  • Avatar of Asixandur Asixandur May 12, 2013 at 08:40 UTC - 0 likes

    @Tharai: Go

    Are you going to fix that, or is it better if we wait 5.3 and see if I can remove your workaround code by using blizz secure dropdowns?

  • Avatar of Tharai Tharai Mar 27, 2013 at 04:17 UTC - 1 like

    I'll try to get around to fixing this this week. Has todo with the code for postponing assignments that would normally taint until out of combat.

  • 3 comments

Facts

Last updated
Oct 31, 2013
Reported
Mar 19, 2013
Status
Declined - We decided not to take action on this ticket.
Type
Defect - A shortcoming, fault, or imperfection
Priority
Medium - Normal priority.
Votes
1

Reported by

Possible assignees