-
-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: Dropdown taints #1
Comments
Well, I have never experienced any kind of taint issues with Sushi dropdowns. Now, if you (or anyone else) find any kind of taint, I will workaround the issue. |
The main point I'm wondering about is the topic discussed in the [US Bug forums][http://us.battle.net/wow/en/forum/topic/6413024969]. Apparently when creating dropdowns with 8 ( = Blizzards default max value) or more options, many secure frames created later on get tainted. In their example it's CompactRaidFrame1, but it can happen with anything using dropdowns (map frame, unit frames, ...). I've often encountered raid frames 1-x (e.g. 3) working fine and suddenly, 4+ are tainted because a dropdown has been initialized in the meantime :( |
Ok, then I will implement it myself. Fairly busy right now fixing MoP bugs and such but, after that, it will be done. |
Oh, this was done a long time ago. Forgot to close. |
I have just stumbled upon this project of yours and am wondering ... Considering the enormous taint issues involved in Dropdown menus and the likes, did you consider this?
I've just had a peek at the code and it seems you rely on Blizzard's Dropdown menu API calls.
I've been looking for functioning dropdowns for a while and don't really want to rely on LibDropDown's predefined table format, so your framework would be heaven-sent if it does work as intended :)
The text was updated successfully, but these errors were encountered: