I've noticed recently that the quest/achievement tracker does not completely close when not tracking. If I close out a quest, a square box remains on screen until I go into the options and disable the two trackers. I can re-enable them and the box is gone but once I begin tracking again, if I close or complete the quest, an empty box remains on screen.
I've deleted all my saved variables and started from scratch, but the mysterious box returns.
I've just posted the first alpha of a complete rewrite of tomQuest2, it will certainly have bugs and currently options are disabled so if you want to try it you'll have to edit the default profile in tomQuest2.lua to change the settings.
edit: this rewrite of tq2 imply a reset of tq2 savedvariables
When I released tomQuest2 for the first time the tracker was quite simple and there was no achievements tracker at this time. But with each release the complexity increased so now you have clickable items, statusbar for achievemnts...
before this release the design principle was like this:
when an event occur all necessary computation are made to update the relevant quest, questobjective and achievements status, and everything was stored in a big table, then the trackers were updated which means every frames of the trackers were first recycled (including statusbar, item icons, collapse icons...) then redrawn which can take time if you for example set your achievement tracker to be part of the quest tracker. same thing if you display by category, when you collapse or expand a category everything is recycled or collapsed. I made this design choice because at this time I was not very fond of frame drawing, positioning so I go the LibQTip way to draw everything. LibQTip is a very good and efficient library which allows me to do some very interesting things with custom cells providers. I made some improvements, like for example at the very begining when I implemented quest timers in the tracker it was redrawn every second which was very bad so I replaced this by a OnUpate script that only redrawn the quest cell every second :)
But it was more and more difficult to improve things and some people complained about performance in some situation so I decided to get back to the drawing board and change the design and now that I'm more familiar with frame manipulation I decided to make my own :)
So the new design is:
When you receive a new quest in your questlog or when you track a new achievements tomQuest2 automatically assign widgets to those for quests trackers, quests tooltip, achievements tracker. those widgets are for quest title and status, quest objectives and quest objectives status, quests items... Those widgets will only be recycled when the quest is no more in your quest log or if you untrack the achievement.
So now when some quest or achievement is updated instead of storing the result in a big table I only update the necessary widget and if needed I'll reposition the widgets in the tracker.
My first impression after testing is that trackers are updated more smoothly and it's using less memory. when playing with the old release I was around 900kb or even above 1mb. with the current alpha I'm arround 550 to 600 kb used.
I still have lots of things to improve but it's on the good way :)
edit: well I forgot I also replaced the module system, it's now back to one file this make this a lot easier as module had too much to exchange so it was an un-needed complexity. (except for option which are still in a separated folder) But I've still some sort of module system so you'll be able to enable / disable part of tomQuest2 as well as automatically disable them in Raid
I had to revert back to TQ v282 because v284 was not working at all for me. I had it enabled, but all it would show was a long rectangular box in the upper right near my minimap and there were no options accessible in interface > addons as there had previously been.
I just commited a new alpha, options are back in and should work :)
frame anchor for tracker are no more, you now directly lock / unlock the trackers in the option panel (you can add a mouse action on both ldb tracker to lock - unlock each trackers), once unlocked you move the tracker directly instead of the anchor frame.
Been playing around with the new alpha for a little bit, but encountering quite a few bugs and errors. I've opened a couple of tickets, but do you want tickets for anything I come across? As I'm assuming that as it's an early alpha it won't be working fully, and I don't want to flood you with tickets for stuff you might already be aware of anyway...