This is the latest version of the new Titan Panel released by the Titan Development Team. The Titan Development Team consists of: HonorGoG, joejanko (Nyte), Lothayer, oXid_FoX, StingerSoft, TristTitan (Tristanian), urnati and YeaChan.
Titan Panel adds a control panel bar on the top and/or bottom of the screen and allows a framework for extensive plugin support.
Features
The ability to have 1 or 2 bars at the top and/or the bottom of your screen.
Many builtin plugins that provide a great core set of features.
Easy to use menus and options to change features on the fly.
Fully supported plugin system. All plugins on the bar are plug-n-play.
Direct all issues and feature requests to the Google Code Titan development page.
Special Instructions
Please read the included TitanPanelSetup-READ_ME_FIRST.txt file for any special instructions needed to use this version of Titan Panel.
Problem Escalation
Please check the Titan Panel Portal for a list of recent issues. These will appear on the main page.
If you are still having issues, please follow the instructions under Bug Reports above.
Included
Core:
TitanAutoHide
TitanPanel & supporting modules
Embedded:
Ace3
AceGUI-3.0-SharedMediaWidgets
LibSharedMedia-3.0
BuiltIns:
TitanAmmo
TitanBag
TitanClock
TitanCoords
TitanGoldTracker
TitanLootType
TitanPerformance
TitanRegen
TitanRepair
TitanVolume
TitanXP
History
A few very dedicated people have maintained Titan Panel over the years. They are in order of chronological responsibility: TitanMod, Dark Imakuni and Adsertor.
Change Log - Titan Panel
Change History
The Titan Panel change history is available at the Titan Panel Portal site.
You may also find the most recent release notes, on our Google code page, here.
We are aware that there is a problem with TitanLootType on the 3.2 PTR. The reason is that Blizzard changed the API and differentiated between dungeon and raid difficulty, in order to facilitate the necessary changes required for the new group/raid instances. We have fixed the plugin internally, so it won't be a problem when we release. Until that time, feel free to disable it from your addon list, if you want to get rid of the error.
Originally posted by Aesir In keeping up with the Joneses, I'd like to ask if Titan Panel's auto-repair feature may be developed to include the ability to set criteria (based on reputation level) to auto-repair at vendors at or above a user-selectable reputation level.
Example:
Set the option to Honored and have it only repair when you have Honored or higher status with that NPC.
We could do something similar sure, but the thing is, it won't be reliable. The addon you listed uses the UnitReaction function to match an NPC's reputation level. The problem with this logic is, the reaction returned does not always correspond to a correct reputation level. As such, any particular setting implemented may not have the desired results.
In keeping up with the Joneses, I'd like to ask if Titan Panel's auto-repair feature may be developed to include the ability to set criteria (based on reputation level) to auto-repair at vendors at or above a user-selectable reputation level.
Example:
Set the option to Honored and have it only repair when you have Honored or higher status with that NPC.
Originally posted by Mikari Hmm getting an error that titan performance is doing something only the blizzard UI can do when trying to promote someone to a main assist in the raid UI.
It's not an error, it's a protected function trying to execute from a tainted execution path. It happens because the number of options in Performance's right-click menu exceeds the initial secure buttons that the Blizzard UI has created. No known workarounds other than reducing the number of those options to an obscenely low number. Just use something else as a main tank setter or disable performance for the duration of the raid (from the character screen).
Hmm getting an error that titan performance is doing something only the blizzard UI can do when trying to promote someone to a main assist in the raid UI.
Originally posted by AnrDaemon If you're using Subversion as your version control system, it can do this for you transparently.
Just attach svn:mime-type=text/plain and svn:eol-style=native properties to the .lua and .toc files.
However, you must make sure that your working copy has consistent line endings before you commit these changes.
Originally posted by Tristanian Heh, sorry about that, we are experimenting with things every now and then, hence the confusion in line breaks, but sometimes all these things never make it to a release for various reasons (eg maybe they break something etc).
If you're using Subversion as your version control system, it can do this for you transparently.
Just attach svn:mime-type=text/plain and svn:eol-style=native properties to the .lua and .toc files.
Last edited by AnrDaemon : 06-05-2009 at 01:37 PM.
Originally posted by AnrDaemon Working with modding Titan Panel in various places, I just discovered that different files has different line endings, even mixed endings sometimes, making it real hard to produce reliable patches.
Heh, sorry about that, we are experimenting with things every now and then, hence the confusion in line breaks, but sometimes all these things never make it to a release for various reasons (eg maybe they break something etc).
Working with modding Titan Panel in various places, I just discovered that different files has different line endings, even mixed endings sometimes, making it real hard to produce reliable patches.
Originally posted by Peyana I'm not really sure where to post this, so will try it here. I try to keep my add-ons as up to date as possible, but have been getting this error the last couple of days:
As far as I know Armory isn't using a Titan specific plugin anymore and the old one has been obsoleted, so you need to delete the "ArmoryTitan" folder from your Interface\Addons folder. Armory will still continue to work with Titan, since it provides and LDB data source feed. Just search your Titan dropdown menu for the "Armory" entry and show the plugin, I have reviewed its code and should work fine
I'm not really sure where to post this, so will try it here. I try to keep my add-ons as up to date as possible, but have been getting this error the last couple of days:
