Yeah I've seen table caching code like that with weak keys before, I just wasn't sure if it was worth it in this case. Also, to respond to Tekkub's suggestion, I need the things to be numerically indexed because a lot of Blizz's handling of quest watches requires it that way.
My addon deals with the quest tracker and currently, to store watched quests, I'm using a table of { questId, timer } where the timer represents a 5 minute timer for automatically watched quests. I realized recently that I was making a new table every time a unique quest watch was added which I feel is probably a bad thing to do. However, I'm confused on ways I could improve this. I was considering making some kind of table cache, e.g., when I stop using a quest watch table, store it in a cache table and retrieve it when I need a new one. However, I don't know if all the table.inserts and table.removes that this would involve would be better than just letting some tiny tables get garbage collected.
So, I have two questions. One, how bad is making a table every time a new quest watch is added (e.g., is it worth changing this at all given that it doesn't happen very often)? And two, what's a good idea for a method to avoid making a new table every time?
I assume it's possible to link the click handler for the buttons in the interface options addon menu, check for a button associated with your addon, and select a particular options frame but I feel like it'd be a lot of effort and some unpleasant hooking for a pretty small gain (if any) in usefulness.
No I don't really have a problem with it, I just didn't know if I could trust the stuff they were giving me and whether it was a legit hosting site or if they were somehow leaching bandwidth.
I got a PM today on WoWI from "wowui.cn" offering me locale files for zhCN and zhTW for my addon, Inquest. Does anybody know if this site is legit? They've posted my addon without asking me (and as far as I can tell, the page doesn't even mention me) but at the same time, they DID do two of the localizations for me. Any suggestions on what to do about this?
I'm getting this issue in the latest version where plugins I have in the center won't show their tooltips if my mouse is all the way on the top of the screen. If I move it down very slightly they show up, but not as far up as I can go.
After some experimentation with Spew, I think GetQuestSortIndex() gives you the number of the header that a quest is under (useful for ExpandQuestHeaders()).
Anybody know what the function GetQuestSortIndex() in WatchFrame.lua does? Also, the comments in WatchFrame.lua now make several references to ExpandQuestHeader sorting the indices. Did something change with this function?
At a friend's request, I was looking at some nameplate mods today to make some updates they wanted and found that both Aloft and another mod I looked at called TidyPlates "find" nameplates by querying all the children of the WorldFrame in OnUpdate (possibly with a throttle timer) and checking some things about the textures those frames have applied. Is there no better way of finding/working with nameplates in the API?
Why do you need the OnUpdate script? As far as I know, RUNE_POWER_UPDATE fires when they go on cooldown AND when they go off cooldown. You can just deal with both cases in that function.
Also, the fact that they come back instantly could possibly be explained by death rune-related talents.
0
0
So, I have two questions. One, how bad is making a table every time a new quest watch is added (e.g., is it worth changing this at all given that it doesn't happen very often)? And two, what's a good idea for a method to avoid making a new table every time?
0
0
0
0
0
0
0
0
0
0
0
0
0
Also, the fact that they come back instantly could possibly be explained by death rune-related talents.