TipTac Reborn

TipTac Reborn

Addons
1M Downloads

TargetFrame SetPoint Lua Errors

Kolmarwow opened this issue · 1 comments

commented

Bug description:
A bunch of SetPoint Lua Errors related to Blizzard's TargetFrame show up when you mouse over it under certain conditions.
Possibly other frames affected too but I've only been able to consistently reproduce this error with TargetFrame.

Steps to reproduce:
This is assuming you only have TipTac & BugSack enabled.

  1. Right Click on TargetFrame -> Click on "Unlock Frame" -> Move it away from the default spot and click on "Lock Frame".
  2. Go into TipTac Options -> Anchors and set Frame Unit Type to Parent Anchor.
  3. Go into combat with a random mob and hover mouse over TargetFrame.
  4. Tooltip bugs out and BugSack starts showing SetPoint errors.

Version:

  • TipTac Reborn 23.05.20
  • WotLK Classic 3.4.1
Error Log 
3x FrameXML/GameTooltip.lua:110: Action[SetPoint] failed because[SetPoint would result in anchor family connection]: attempted from: GameTooltip:SetPoint.
[string "=[C]"]: in function `SetPoint'
[string "@FrameXML/GameTooltip.lua"]:110: in function <FrameXML/GameTooltip.lua:108>
[string "=[C]"]: in function `GameTooltip_SetDefaultAnchor'
[string "@FrameXML/UnitFrame.lua"]:304: in function `UpdateTooltip'
[string "@FrameXML/GameTooltip.lua"]:444: in function <FrameXML/GameTooltip.lua:423>
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: ?

Locals:
(*temporary) = GameTooltip {
 0 = <userdata>
 ttSetIconTextureAndText = <function> defined @TipTacItemRef/ttItemRef.lua:309
 SetSpellBookItem = <function> defined =[C]:-1
 OnBackdropLoaded = <function> defined @SharedXML/Backdrop.lua:152
 default = 1
 GetBackdropColor = <function> defined @SharedXML/Backdrop.lua:390
 SetHyperlink = <function> defined =[C]:-1
 SetUnit = <function> defined =[C]:-1
 hasMoney = 1
 TopLeftCorner = Texture {
 }
 RightEdge = Texture {
 }
 SetOwner = <function> defined =[C]:-1
 SetBackdropBorderColor = <function> defined @SharedXML/Backdrop.lua:422
 ApplyBackdrop = <function> defined @SharedXML/Backdrop.lua:294
 SetBackdrop = <function> defined @SharedXML/Backdrop.lua:329
 ClearBackdrop = <function> defined @SharedXML/Backdrop.lua:282
 TopOverlay = Texture {
 }
 GetBackdropBorderColor = <function> defined @SharedXML/Backdrop.lua:409
 GetBackdrop = <function> defined @SharedXML/Backdrop.lua:347
 SetUnitDebuff = <function> defined =[C]:-1
 SetQuestItem = <function> defined =[C]:-1
 BottomLeftCorner = Texture {
 }
 SetBorderBlendMode = <function> defined @SharedXML/Backdrop.lua:266
 FadeOut = <function> defined =[C]:-1
 numMoneyFrames = 1
 BottomEdge = Texture {
 }
 SetPetAction = <function> defined =[C]:-1
 comparing = false
 SetQuestCurrency = <function> defined =[C]:-1
 shoppingTooltips = <table> {
 }
 SetQuestLogCurrency = <function> defined =[C]:-1
 SetQuestLogItem = <function> defined =[C]:-1
 Center = Texture {
 }
 OnBackdropSizeChanged = <function> defined @SharedXML/Backdrop.lua:182
 HasBackdropInfo = <function> defined @SharedXML/Backdrop.lua:278
 backdropInfo = <table> {
 }
 BottomOverlay = Texture {
 }
 SetAction = <function> defined =[C]:-1
 ttIcon = Texture {
 }
 GetEdgeSize = <function> defined @SharedXML/Backdrop.lua:188
 NineSlice = Frame {
 }
 SetupTextureCoordinates = <function> defined @SharedXML/Backdrop.lua:214
 TopEdge = Texture {
 }
 ttCount = FontString {
 }
 TooltipBackdropOnLoad = <function> defined @SharedXML/SharedTooltipTemplates.lua:172
 SetUnitAura = <function> defined =[C]:-1
 TopRightCorner = Texture {
 }
 updateTooltip = 0.200000
 SetUnitBuff = <function> defined =[C]:-1
 needsReset = true
 BottomRightCorner = Texture {
 }
 SetBackdropColor = <function> defined @SharedXML/Backdrop.lua:399
 LeftEdge = Texture {
 }
 SetupPieceVisuals = <function> defined @SharedXML/Backdrop.lua:246
}
(*temporary) = "BOTTOMRIGHT"
(*temporary) = "UIParent"
(*temporary) = "BOTTOMRIGHT"
(*temporary) = -13
(*temporary) = 70
commented

Thanks for reporting and describing the steps to reproduce this! Without this information it would probably be impossible to solve this. 👍

Indeed the error message regarding SetPoint() only pops up for parent anchored tooltips if the target frame has been moved away and only in combat. Unbelievable... 😄

I have been able to fix this. Will be included in the next release.