The bottom bar seems to adjust fine now. I'll keep an eye on it. Thanks.

I have added a number of fixes and a couple of new features in 4.2.2, most notably support for guild bank repairs and an option to toggle the text completely off from Data Broker plugins marked as "data sources" (apparently a lot of people wanted it, judging from the number of mails I got), among other things. As I'm in a position where I cannot test everything 100%, feedback is always appreciated (as usual we do read and consider everything, despite not always replying).

Oh yeah the viewport idea was just something that went through my mind at the time, didn't really think it through. I do like the strata idea though. Heck, it could even be limited to just the Flame Leviathan and Malygos fights. But regardless, those are just ideas, I understand the limitations and can live with them.

It's been a long time since I've used a bar addon. Didn't like them at the time. Maybe I should look again, but I'm one of the few who's satisfied with the default action bars. Perhaps it's because I have enough real estate since I use a 22" monitor.

Regarding the bug still happening, ok, I'll try the next release. It does seem better than it was and I hate to make a huge deal of it: it's not game-breaking.

Aye, that's what I'm doing as well and in all honesty I'm encouraging people to use addons that hide the MainMenuBar and allow them to place their own custom spell and ability bars wherever they like and set them up however they like. We will always try to provide a "solution" for users that like the default UI but there are limitations that we cannot ignore. That being said, I tested a viewport solution but sadly the result is a bit ugly, visually so I'm back into refining the current fixes in place.

I do not know how I got by without this in the past. Great mod you got here by far one of the best ones I have ever used.

Keep up the good work.

There seems to be some problem with your installation, as either an Ace3 library cannot be located or for some reason, the localization files are not properly registering translation before the main code fires. Suggestion is to perform a clean (re)installation.

This is the error i am receiving

Date: 2009-04-27 21:56:35
ID: 1
Error occured in: Global
Count: 1
Message: ..\AddOns\Titan\TitanPanel.lua line 144:
attempt to index local 'L' (a nil value)
Debug:
[C]: ?
Titan\TitanPanel.lua:144: in main chunk
AddOns:
Swatter, v5.1.DEV.150
Atlas, v1.13.0
Titan, v4.2.1.30100 - Revision 234
(ck=4e)

I have removed pretty much all of my add-ons and I'm still getting this error. Can someone help me out please.

Medium-level approach would be to optionally use viewport adjustment for bottom bar only.
The issue itself, as I see it (haven't been hit by it at all) is only happened when you're using bottom bar with default Blizzard button frame.
I'm not using it since I've discovered Bartender and i didn't have any issues with jumping frames at all. (Bartender use it's own positioning system)

Hmm, going to try increasing the delay to 5 seconds after player entering world, when the adjustment fires in the next release, see how that goes.

Hmm, it is feasible but as you mention it may put some people off, so I don't know if its a good idea forcing it. And yeah it sucks when that happens, for leviathan that is, but can't really do much, Blizzard will not let just re-anchor the frames in combat. An idea would be to temporarily set the strata of the panel to "LOW", so that the Vehicle bar will simply "cover" it, while in combat. It's sucky from the point that will cover plugin information, but at least it will enable you to play unobstructed.

Finally, after third time, it worked... thanks for your effort, though...

Disable Colorblind mode.

Tristanian, sorry... but it happened again. The bottom bar issue, that is. It happened when taking a mage portal from Naxx to Dalaran.

At this point, I'm considering switching to the top bar anyway. Not because of this intermittent bug, but because when going in/out of a vehicle while in combat prevents the bar from adjusting anyway (Flame Leviathan fight if you're getting thrown on top of him, Malygos...). The only other idea I can suggest is to make Titan act like a viewport for people who don't have the bar(s) set to autohide. I.E. make the game window smaller and Titan be outside of it. I don't know how feasible that is, though I know there are/were viewport addons. I'm not sure it's desirable anyway. Perhaps as an option, but that's a lot of work for you guys too.


I've asked X-Perl's author to change it and it has now been done in the latest alpha.

Thanks for the support. Just wanted to make clear that I don't have a problem with implementing new features that I know I will even use myself at least once The thing is when implementing something, I also need to consider what implications this will have on the majority of the users and whether implementing it, is likely to cause issues and (directly or indirectly) break functionality in other places. All in all, it's never personal.

As for the money icons in GoldTracker do you mean you are unable to see the tooltip properly or the button itself ? What client language are you using (if not English) ?

Thank you for providing this great add-on to those of us who have no idea how to do these types of things. I was reading comments and saw the first couple and decided that you guys needed a "hurrah" instead of "I want more, more, more!"

I use this and the plug-ins you provide as well as every other add-on I have that will plug in to Titan. I set the bar to hold just icons all across the bar, so the way it works is great with me!

One question though---money in game shows as ??g??s??c instead of ??icon??icon??icon. Did that change within WoW, or have I missed a new setting?

Right-side plugins imply icon only so, no. "Data Source" plugins are supposed to return some kind of significant text information, in addition to providing a tooltip. It is true that there are authors out there using the "data source" type, for no apparent reason, when in reality their plugins just perform an action upon clicking and maybe provide a tooltip, which is plain bad design on their part. I don't see why I should spend hours upon hours modifying the design of my code, which conforms to the LDB spec, thus risking introducing new bugs, just to indirectly encourage bad design. I simply won't do it.


If you feel that the plugins are providing needless or redundant information, then once again, you should speak to the plugin authors, to implement options to hide that kind of text (I know at least I have done that for Broker_Factions) or simply revert the data object type, to "launcher", which only provides an optional label that can be hidden by displays.