Talent Tree Tweaks | Dragonflight

Talent Tree Tweaks | Dragonflight

2M Downloads

Edit loadout button broken in 10.2

cremor opened this issue ยท 10 comments

commented

After patch 10.2 the edit button for the talent loadout is broken. When I click it, no dialog is opened but instead the loadout vanishes from the list.

When I disable the Talent Tree Tweaks addon the button works correctly again.

Here is an screenshot after I clicked the button on 3 loadouts:
grafik

commented

Having the same issue with v1.10.5 of the addon.
No errors are being triggerd

commented

I'm seeing the same thing, will look into it tomorrow :)

commented

turns out there was a problem in the DropDown lib I use, fixed now

commented

Seems like addons with broken version of the LibUIDropDownMenu library were the culprit for me @cremor . Modifying LibUIDropDownMenu.lua per this issue in each of their local library files resolved it. The culprits in my specific case were AngryKeystones, TwitchEmotes, and RareScanner. Don't think there's anything else to be done on your end @Numynum just need affected addon authors to fix. Appreciate your work!

commented

But shouldn't the updated version inside TalentTreeTweaks replace the old lib version in all addons automatically? Unless the modifications done by @Numynum to the lib prevent that.

commented

@Numynum I've updated to v1.10.6 and it's fixed for most talent loadouts. But the very first loadout in the list still shows the same issue.

commented

odd, it's working fine for me
is it also broken with all other addons disabled?

commented

Not, it indeed works fine with only Talent Tree Tweaks loaded.
I couldn't yet figure out which specific other addon triggers the bug. I first suspected other addons using LibUIDropDownMenu but it looks like that's not it.

commented

Yeah, seems I rushed out the fix a bit too quickly ๐Ÿ™‚
I might find some time to fix it properly today, but might have to wait for tomorrow
(I decided to fork the library, and thought I changed all the shared variables to something unique, but clearly I missed some; didn't have the time to test with an addon using the original lib)

commented

should be fixed properly now