Sorry to hijack the thread, but a related question. During testing/updating/etc of SmartRes2, if I use my slash commands (/sr and /smartres) sometimes they open right to the SmartRes2 panel, and sometimes they open to Interface.. Addons, and you have to scroll down to the SR2 entry. It isn't consistent, and I did notice an addon on curse.com that "fixes" this, but I do not have it installed.
Any ideas why the inconsistency? Furthermore, if it does not open right the panel on first slash use, it will every time after I use a slash after. It is the first time that sometimes it works, sometimes it doesn't.
Sorry to hijack the thread, but a related question. During testing/updating/etc of SmartRes2, if I use my slash commands (/sr and /smartres) sometimes they open right to the SmartRes2 panel, and sometimes they open to Interface.. Addons, and you have to scroll down to the SR2 entry. It isn't consistent, and I did notice an addon on curse.com that "fixes" this, but I do not have it installed.
Any ideas why the inconsistency? Furthermore, if it does not open right the panel on first slash use, it will every time after I use a slash after. It is the first time that sometimes it works, sometimes it doesn't.
iirc it's because of weirdness when using InterfaceOptionsFrame_OpenToCategory with too many categories, you might be noticing this discrepancy because you don't have a panels sub panels expanded.
I'm wondering if there is a way to force the SmartRes2 (or any addon) category to open on the appropriate slash command. If not, I can live with a mild annoyance.
Don't: Copy/paste the addon's code, or "embed" it in your addon. While it may initially seem like a good idea to fix Blizzard's bug for your users, you should consider that (a) not all users are even affected by the bug, so including code to fix it would just be bloat for those users, (b) the fix may conflict with other addons users have, so including it prevents those users from using your addon and their other addons, and (c) the fix is not directly related to your addon, so including it is still bloat. Not assuming you were going to include it, but after the rash of addons embedding BetterBlizzOptions to the extent that an addon was created for the sole purpose of "removing" it, I feel it's worth mentioning.
Also, I've moved the posts on this subject to a new thread, because "why does my slash command sometimes open to the wrong panel?" doesn't belong in a "how do create sub panels in my options?" thread.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorAny ideas why the inconsistency? Furthermore, if it does not open right the panel on first slash use, it will every time after I use a slash after. It is the first time that sometimes it works, sometimes it doesn't.
iirc it's because of weirdness when using InterfaceOptionsFrame_OpenToCategory with too many categories, you might be noticing this discrepancy because you don't have a panels sub panels expanded.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorLibStub("AceConfig-3.0"):RegisterOptionsTable("SmartRes2", options) self.optionsFrame = LibStub("AceConfigDialog-3.0"):AddToBlizOptions("SmartRes2", "SmartRes2") self:RegisterChatCommand("sr", function() InterfaceOptionsFrame_OpenToCategory(self.optionsFrame) end) self:RegisterChatCommand("smartres", function() InterfaceOptionsFrame_OpenToCategory(self.optionsFrame) end)I'm wondering if there is a way to force the SmartRes2 (or any addon) category to open on the appropriate slash command. If not, I can live with a mild annoyance.Unrelated: what does "iirc" stand for?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumDo: Tell your users to install the addon that fixes it.
Don't: Copy/paste the addon's code, or "embed" it in your addon. While it may initially seem like a good idea to fix Blizzard's bug for your users, you should consider that (a) not all users are even affected by the bug, so including code to fix it would just be bloat for those users, (b) the fix may conflict with other addons users have, so including it prevents those users from using your addon and their other addons, and (c) the fix is not directly related to your addon, so including it is still bloat. Not assuming you were going to include it, but after the rash of addons embedding BetterBlizzOptions to the extent that an addon was created for the sole purpose of "removing" it, I feel it's worth mentioning.
Also, I've moved the posts on this subject to a new thread, because "why does my slash command sometimes open to the wrong panel?" doesn't belong in a "how do create sub panels in my options?" thread.