BUG: UFOs in the catalog are frozen

[ScottIngram]

Thanks to hayleqwyn on Curse for this report:

Ever since the update that made it so flyouts will wrap to additional rows/columns if they have a lot of buttons, I am no longer able to edit any flyouts. When I click on them in the UFO frame, they open, but I can't interact with them at all beyond that. No errors seem to be getting thrown.

So I asked:

• does this happen for the UFO catalog regardless of how you got there? For example, the UFO catalog appears on Bliz's macro window, the spell book window, the collections window.
• can you drag new buttons into your UFOs?
• can you create new UFOs? If so, does this bug happen for those too?
• um... any other weirdness happening?

In reply to scott_ingram: I haven't had a chance to log in yet today but last I checked the answers were:

• Yes, it happens no matter which base frame I'm accessed it through.
• No, I cannot add new buttons to my existing flyouts. I also cannot remove or reorder existing buttons.
• I haven't tried creating any new flyouts since the issue started, so I don't know the answer.
• While the flyouts all work properly when placed on action bars and have all their buttons displayed properly, when opening them through the UFO frames, many of the existing buttons aren't being displayed.

I finally got back on and have found that:

• The issue is still happening in the new version.
• I CAN create new flyouts (and delete flyouts), but the issue affects them as well.

I'm not sure if the issue might be a result of a weird interaction from another addon but, since this issue was a recent development, I can tell you these are the addons I have recently installed:

• LiteMount
• WoW Notes
• Flightsim
• Home Bound
• Decor Vendor
• WoWthing Collector
• OPie
• Spade

UPDATE: I have tried disabling all of those addons, but I still am having the issue with editing flyouts. I also tried disabling LargerMacroIconSelection and Macro Toolkit (both of which I have found conflicted with UFO before, though I pointed them out and you added checks for them), but that also didn't fix it. As one last attempt, I going to try deleting the UFO saved variables and see if that fixes it.

UPDATE 2: Deleting the existing saved variables did not fix the issue either. So I am truly stumped here about what is causing the problem.

[ScottIngram]

I hadn't seen this problem, then, suddenly it happened for me while I was working on outfits, then, it simply went away again. I tried going reverting the code back to each and every version since the wrap-around release, but can't make the bug come back.

So, I haven't found the cause yet.

I will keep trying because this is a total show stopper for anyone who runs into it, especially a new user. Thanks again for the report because I might have never known.

[Hayleqwyn]

Glad to be able to help bring the issue to your attention. I'm a programmer myself but, for code I didn't write and without any errors being thrown, I couldn't really determine where to even start, beyond simply checking all the things I reported on previously. If I notice any other relevant details about the issue, I will be sure to share them here. Hopefully you can figure this issue out since, as you mentioned, this error truly does impact the ability to use the addon. And I really enjoy the addon's functionality, so I really want to be able to continue using it.