Bunch of old addons are broken because of the new SetPoint restrictions, throwing errors like “Action[SetPoint] failed because[SetPoint would result in anchor family connection]:”
How are these supposed to be fixed?
Bunch of old addons are broken because of the new SetPoint restrictions, throwing errors like “Action[SetPoint] failed because[SetPoint would result in anchor family connection]:”
How are these supposed to be fixed?
I’ve been hunting and reply watching all afternoon to see if I can find something. MoveAnything is shot now.
I fixed TrinketMenu by adding TrinketMenu_MainFrame:ClearAllPoints() before the offending SetPoint call. I imagine that could end up messing up whatever point was ‘bad’ though.
Seems to be mostly a problem with SetPoint used with UIParent, even for frames that are parented to that?
Based on the error I’m getting it looks like it’s tied to UIParent, but I don’t know anything about addons to be able to do more than duplicate someone else’s instructions for fixing something really. I’m comfortable enough to make an edit to a file, not knowledgeable enough about the subject to make the change solo.
It’s a restrictinon they added to anchor points, see the sticky at the top of the forum. I suspect MoveAnything may be fundamentally broken / impossible now.
MoveAnything is working fine for the small number of frames that I use it for.
The sticky only lists nameplates as subject to the new restrictions. I wonder if other frames are restricted but not listed in the sticky.
What are you trying to move?
Oddly enough I’m getting the error coming from something I’ve never moved. It tells me there’s a problem with MainActionBar1 and I can’t reset it in MA or otherwise do anything about it. But I’ve never moved it to begin with.
Just because you’ve never moved it doesn’t mean MA didn’t build a mover for it.
Try running with Move Anything disabled and see if the problem goes away.
I realize they “built a mover for it” since they built a mover for every element of the UI. I was replying to someone who said “it’s working fine with the limited number of things they have moved”. But thanks.
That’s what I was responding to. Your point seemed to be that because you’d never moved it, it shouldn’t be erroring out. My point was that if MA makes a mover for it, it doesn’t matter if you ever tried to move it or not.