MobMap v3.14...and v3.15
Thursday, November 27. 2008
More bugfixing (and a little polish) to the quest tracker in this version. I really hope to have this new feature finally stabilized now, with no more new bugs popping up.
If that turns out to be true, I can start thinking about adding more features. I have read a lot of suggestions with good ideas from people who like the idea of the new tracker (and those who don't or already have a quest tracker which they like more can disable the MobMap one with a single click now), and I will most probably integrate some of those. But because I wanted to do that on a stable basis, I had to get the bugs sorted out first. The suggestions and general feedback though tell me that I did do the right thing by creating the tracker in the first place - even though some people understandably don't have any use for it.
Be sure that I will have a close look at the memory footprint of the tracker during development, just as I always have on any MobMap component. If the tracker should later become too much of a memory hog, I will separate it from the main MobMap database browser into a new Load-on-Demand-AddOn just like I separated the database parts long ago first from the browser itself, then from each other, in order to just load what's absolutely necessary. But I don't want to further clutter peoples' addons directory if it's not really necessary and worth it.
The new version is already online for download via the MobMapUpdater, the manual download packages and the installer package are created automatically and will be up in a few hours, too.
Oh, and there's something some people have noticed and told me about: MobMap lacked knowledge of some NPCs, even when those were mainstream and should have been in the database. This was mainly due to a bug in the data collection routines of MobMap which has been fixed in MobMap v3.10. The data uploaded from 3.10 versions of MobMap had to wait in a processing queue though, as the MobMap server is currently still running on full load and catching up on the big amounts of data uploaded past the WotLK release. But right now the first several thousands of 3.10 uploads should have been processed, adding a lot of the missing NPCs to the database - you might notice the jump in the NPC counter :o) To get to the point: I highly suggest updating your database when updating to v3.14.
----------------------------------------------
v3.14:
- fixed: The error that has been shown when switching to the pickup database manually has been fixed
- changed: Quest targets (like "Kill 10 foozles: 0/10") will now line-wrap in the quest tracker to always allow you to read the full text
- changed: Scrolling in the quest tracker has been changed from line-based scrolling to pixel-exact scrolling
- fixed: Displaying pickup item positions in multiple zones simultaneously does now work again
v3.15:
- fixed: The scrollbar issues in the quest tracker have been solved somehow. Unfortunately hiding the scrollbar and using the space to make the text a little bit wider didn't work out as desired with the line-wrapping quest targets, so I switched to a static text width for the moment, still only showing the bar when it's required though.
If that turns out to be true, I can start thinking about adding more features. I have read a lot of suggestions with good ideas from people who like the idea of the new tracker (and those who don't or already have a quest tracker which they like more can disable the MobMap one with a single click now), and I will most probably integrate some of those. But because I wanted to do that on a stable basis, I had to get the bugs sorted out first. The suggestions and general feedback though tell me that I did do the right thing by creating the tracker in the first place - even though some people understandably don't have any use for it.
Be sure that I will have a close look at the memory footprint of the tracker during development, just as I always have on any MobMap component. If the tracker should later become too much of a memory hog, I will separate it from the main MobMap database browser into a new Load-on-Demand-AddOn just like I separated the database parts long ago first from the browser itself, then from each other, in order to just load what's absolutely necessary. But I don't want to further clutter peoples' addons directory if it's not really necessary and worth it.
The new version is already online for download via the MobMapUpdater, the manual download packages and the installer package are created automatically and will be up in a few hours, too.
Oh, and there's something some people have noticed and told me about: MobMap lacked knowledge of some NPCs, even when those were mainstream and should have been in the database. This was mainly due to a bug in the data collection routines of MobMap which has been fixed in MobMap v3.10. The data uploaded from 3.10 versions of MobMap had to wait in a processing queue though, as the MobMap server is currently still running on full load and catching up on the big amounts of data uploaded past the WotLK release. But right now the first several thousands of 3.10 uploads should have been processed, adding a lot of the missing NPCs to the database - you might notice the jump in the NPC counter :o) To get to the point: I highly suggest updating your database when updating to v3.14.
----------------------------------------------
v3.14:
- fixed: The error that has been shown when switching to the pickup database manually has been fixed
- changed: Quest targets (like "Kill 10 foozles: 0/10") will now line-wrap in the quest tracker to always allow you to read the full text
- changed: Scrolling in the quest tracker has been changed from line-based scrolling to pixel-exact scrolling
- fixed: Displaying pickup item positions in multiple zones simultaneously does now work again
v3.15:
- fixed: The scrollbar issues in the quest tracker have been solved somehow. Unfortunately hiding the scrollbar and using the space to make the text a little bit wider didn't work out as desired with the line-wrapping quest targets, so I switched to a static text width for the moment, still only showing the bar when it's required though.

