Thanks to Calian of the Insomniax forums for posting a how-to on Trinity that I have used as a basis for this document and even used some of his text because I could not explain it better =)

*******************

If you are configuring Trinity for a stance/form class, it is recommended to launch WoW with just the default interface to do a bit of preparation, especially if you have used other action button addons. What you want to do after starting WoW is to check all your stances to see if the default UI contains the stance's appropriate abilities. Some action button addons do not follow Blizzard's convention for the use of button ID's, but Trinity does. If you want to skip this step, you may, but it requires a willingness to gain a solid understanding of how Trinity works.

When you first launch TrinityBars it is in Config Mode. This is easy to spot because there is a box around each bar (called a dock) with small icons for adjusting button attributes such as scaling, number of buttons, configuration (horizontal/vertical/circular), hide until mouse-over, and a label that tells you what state the dock is in (Stance/Paged/Normal(Bar#)).

The first lesson is how to exit configuration mode. It is important to not play the game while in configuration mode, as this mode is doing a lot of work in the background and can easily bog you down if played in the mode. To enter or exit the config mode, you simply click on Trinity's minimap button on the minmap to open up a sub menu of options. If you do not see the button on your minimap it may be underneath another addon's minimap button, however it will always be on top of Blizzard's minimap icons. The minimap button looks like either a blue angel or blazing blue "T". With the minimap sub-menu open, the button at the very top will enter or exit configuration mode (currently this button looks like gray blinds).

[COLOR=Cyan]Global options using the minimap menu -[/COLOR]

	[INDENT]With the minimap sub-menu open, you will now see seven sub-menu options.

	Going clock-wise starting at the top:

	[COLOR=Cyan]"Blinds" icon[/COLOR] (better image to come =) ) - This button will enter or exit configuration mode. Shift-Clicking this button will toggle wheather or not you want to show/hide button tooltips.
	
	[COLOR=Cyan]Lock icon[/COLOR] - This button will lock or unlock the actions on your action buttons from being dragged out of a button.

	[COLOR=Cyan]Tri-arrow icon [/COLOR]- This button will globally cycle through available button graphics. This includes standard square, trimmed-square and round image graphics and may include more images in the future.

	[COLOR=Cyan]No Icon Yet[/COLOR] - This is the future option for loading/saving layout templates.

	[COLOR=Cyan]No Icon Yet[/COLOR] - This option opens up another submenu of options to handle the docking frames.

	[COLOR=Cyan]Key icon[/COLOR] - This button will enter or exit key binding mode. When in key binding mode the action buttons all enter a "waiting" state. As you mouse over the buttons, the tooltip will indicate which numbered button you are over and give you brief instructions on how to bind a key. While in key binding mode ANY KEY YOU PRESS WHILE THE MOUSE IS OVER THE BUTTON will be assigned to that button. It is recommended that you do your key binding when you do not have to use your keyboard for anything else - like moving or chatting. If you do happen to accidentally bind a key unintentionally and unbind it from Trinity's button, Trinity releases the key back to Blizzard's default key binding interface where you will have to go to rebind that action. Information about binding action buttons used in stances or paging to follow.

	You may also use Trinity's binding mode to bind key's directly to spells, no button required. Simply open your spellbook and with key binding mode on, mouse over your spells and the tooltip will provide feedback on how to bind a key to the spell. Direct macro and item binding are in the works.

	Also, Shift-Clicking this icon will either hide or show the key-binding text on action buttons.

	[COLOR=Cyan]Hands Icon[/COLOR] - This button will cycle through various self-cast options. They are None, RightClick, Alt-LeftClick, Alt-RightClick, Ctrl-LeftClick, Ctrl-RightClick, Shift-LeftClick, Shift-RightClick. It is important to note that keybinds in 2.0 are processed like mouse-clicks, so these self-cast options will also work for keypresses as well as mouse-clicks.
	
	[COLOR=Cyan]Detaching menu options from the minimap button -[/COLOR]
	If desired, you may detached the sub-menu options from the minimap button. To do this, Shift-LeftClick-Drag on the minimap button away from the minimap. This will result in a second Blue Angel/Blazing Blue "T" icon surrounded by the sub-menu that is freely moveable. The second Blue Angel icon still has all the click behavior of the one still attached to the mini-map save for that the minimap icon can hide/show the second Blue Angel icon AND the sub-menu options.
	
	Once you stop dragging the mobile options button, the minimap button will hide itself. It will reshow itself when you drag the mobile button again incase you want to re-dock it. To redock the sub-menu to the minimap button, simply drag the second Blue Angel icon to the one still attached to the minimap and when it gets close enough it will snap into position with the minimap button.[/INDENT] 

[COLOR=Cyan]Learning How To Configure Each Bar:[/COLOR]

	[INDENT]When you are in configuration mode will notice a box around each bar. These are the docks that the buttons use to position themselves in relation to. You will notice all sorts of smaller objects to either side of the buttons. These control how the buttons behave or look. Mousing over these small objects will display a tooltip with abbreviated instructions and relative data for the action it performs. Also, any action done by these buttons that changes the size of the dock will initiate a .75 second delay before the dock adapts to it's new shape. This is to allow using a button with successive clicks without it jumping away from your mouse cursor.

	[COLOR=Cyan]Left-end side of the button dock, from left to right-[/COLOR]

		[INDENT][COLOR=Cyan]Up and down arrows:[/COLOR]
		These buttons can do two things. The can adjust the scale of the buttons (make them smaller or larger) and adjust the visibility of the buttons (opacity) To increase the scale, press the up arrow, to decrease press the down arrow. To increase opacity, shift-click the up arrow, to decrease opacity, shift-click the down arrow.

		[COLOR=Cyan]+/- buttons:[/COLOR]
		These buttons also have two functions. Primarily they will add or subtract buttons from a dock. In order to add buttons to a dock, you must have buttons available. The tooltip will indicate how many buttons you have available to add. Upon initial launch of Trinity, you will have zero buttons to add, as all 120 button objects have been pre-allocated to bars. To subtract buttons from a bar, simply click on the minus button and the buttons are stored in a central pool of buttons that is not visible to you. Your only information of this central pool is the tooltip telling you how many buttons are available. To remove all buttons on a bar at once, alt-click the minus button.

		The other function these buttons perform is to adjust horizontal and vertical spacing between the buttons. To do this requires a shift-click. Shift-Left clicks will adjust horizontal spacing and Shift-Right clicks will adjust vertical, the plus button increasing spacing and the minus button decreasing spacing.

		[COLOR=Cyan]Check box next to + button:[/COLOR]
		This check box does one simple thing and that is to either show or hide the button grid for the dock. What this means that if it is checked, the empty buttons will still show their empty button graphics, while unchecked it will hide them upon exiting configuration mode.

		[COLOR=Cyan]Tri-arrow circular button next to the - button:[/COLOR]
		This button will cycle through available button graphics to the buttons on the docks. This includes standard square, trimmed-square and round image graphics and may include more images in the future.[/INDENT]


	[COLOR=Cyan]Right-end side of the button dock, from right to left -[/COLOR]

		[INDENT][COLOR=Cyan]Rotate left/right buttons:[/COLOR]
		These two buttons will change the configuration of the buttons. Currently you may arrange the buttons in their default singular horizontal row, a vertical singular row, a multi row/column block, a circle and various arcs. taking advantage of the .75 second delay previously mentioned, you can quickly cycle through the configurations, but when you stop, the dock will then adjust it's shape to the new configuration, which could dramatically change the position of the configuration options.

		[COLOR=Cyan]The "stealth" icon:[/COLOR]
		This button will tell the buttons to auto-hide until moused over when checked.

		[COLOR=Cyan]The Dock Label:[/COLOR]
		This is a very important button as it can change some fundamental elements of how the buttons behave. Currently, this button can change the bar type or it can specify a specific target type for the buttons of that dock.

		[COLOR=Cyan]Changing Bar Type - The Header Editor[/COLOR]
		To open the header editor, shift-click the bar label. A box will appear to the right of the dock frame. This editor allows for some very flexible modes for the bar. But, first an explanation.

			[INDENT]With WoW 2.0, a new feature in the API was introduced called headers. These headers are in charge of the buttons of any given dock frame. The headers get information from WoW and tell the buttons how to react. However, the headers need some basic rules to follow and this is where the header editor comes in.

			The header editor in Trinity is written to allow you, the end user, control over how the header behaves. You can imagine this header editor like a chain of command. The header that is at the top is the ultimate boss, what it decides to have happen will affect all other active headers. The lowest active header only has control over itself.

			Each dock frame can have active up to 7 different types of headers, 6 of which you can change how they behave.

			1) Normal Header: This is a special type of control header whose only purpose is to serve as a foundation for the header system. It's variables are constant and unchanging, so we can't change anything for it.

			2) Stance Header: This header gets it's information on how to behave based on stances or forms a class may have. Internally, these stances and forms are represented by a number. Whatever the current stance/form will always be shown as a green number in-between two gray ones.

			3) Paged Header: Internally, WoW has 6 page states available for making bars that respond to page change requests. The page changes are driven by key bindings found in the default UI key binding interface. By default, to change pages is shift-mousewheel or shift-page#. The current page that WoW is on is displayed as the green number between the two gray ones.

			4) Stealth Header : This header gets it's information on whether a character is in a state of stealth or not. Stealth as far as WoW is concerned is any ability to hide yourself from view. Rogue stealth, Druid prowl, Night Elf shadowform are all treated the same. Stealth state is represented by either a 0 or a 1.

			5,6,7) Alt, Control, Shift headers: These three headers get their state on whether or not their respective key is held down or not. WoW will consider the number 0 as the key is NOT held down, while the number 1 is with the modifier key pressed.[/INDENT][/INDENT]

		[COLOR=Cyan]SIMPLE BARS:[/COLOR]

			[INDENT]If you just want a simple bar, all you really need to do is just make active one header.

				[INDENT]-Making the Paged Header active will give you a paged bar.
				-Making the Stance Header active will give you a stance bar.
				-Making one of the modifier key headers active will give you a bar that will toggle buttons when the modifier key is pressed.

				And that's it![/INDENT][/INDENT]

		[COLOR=Cyan]COMBINED HEADERS BARS:[/COLOR]

			[INDENT]Here are two simple to set up common combined header bars.

				[INDENT]To make a druid form bar with prowl:

				-Make the stance header active.
				-Change to cat form.
				-Make the stealth header active.
				-Change the last number (the showstate) to the green number the stance header displays. Typically 	for a druid cat form is 3.
				-Go into prowl and add your prowl buttons.

				To make a paged bar that will "pop-up" a bar when alt,ctrl or shift is held down:

				-Make the Alt, Ctrl or Shift header active.
				-Make the paged header active. Insure the last number (the showstate) is the same as the green number for the modifier header, which should be 0 for when the key is NOT held down.

				And we are done![/INDENT][/INDENT]
				
			[INDENT]All you need to do now is go through each form, page or modifier page and add or remove buttons as needed.[/INDENT]

		[COLOR=Cyan]A COMPLEX HEADER:[/COLOR] 

			[INDENT]Now to combine the above two headers. We will make a stance, paged, stealth and modifier bar combined.
		
			[INDENT]- Make the Alt, Ctrl or Shift header active, make sure it's showstate is 0
			- Make the the paged header active, Make sure it's showstate is also on 0.
			- Make the stance sheader active. Make it's showstate on whichever of the 6 pages of the paged header you 		want. 1 is typical.
			- If you are a druid, switch to cat form now.
			- Make the stealth header active. Set it's showstate to whatever the current green number is for the stance header.

			Not too hard =)[/INDENT][/INDENT]
			
		An important fact to remember is that anytime you deactivate a header, any buttons associated with that header will be stored. You cannot backtrack. So it is best to decide how you want to set up your bars, watch the bar label to verify it is going through the motions you want it too, then add/remove buttons.

		[COLOR=Cyan]Changing Target Type-[/COLOR]
		To  change the target type of a bar, click on the bar label until you see a target type. Usually this will be "None" as we have yet to set a target for the bar. To cycle through the available target types, use the rotate left/right buttons near the bar label. When you do set a target type for a bar, do not expect it to behave like a normal bar when the target does not exist. What usually happens is the spell will just not cast.
		
			[INDENT]Mouse: - this can be a most useful target type, so I put it first =)
			This will attempt to perform any action on this dock if a qualified unit for that action exists under the mouse cursor.  If no unit exists under the mouse cursor, nothing happens. What this allows you to do is cast spells very quickly. For example, if you are in a raid and are assigned to remove curses, you can monitor curses by whatever means allowed, and when you want to cast remove curse, just move your mouse over the target or the target's party frame, and press your key-bind for remove curse. You do not need to make the target your current target or even mouse click to cast the spell.

			None:
			This specifies no target. Actions will operate with standard targeting behavior.
	
			Self:
			This will attempt to perform any action on this dock on the player's character. This is meant for perma-selfcast buttons. If you want to use the spells for other players, then set the self-cast option as mentioned above.
	
			Pet:
			This will attempt to perform any action on this dock on the player's pet.
	
			CurTgt:
			This will attempt to perform any action on this dock on the player's current target. This type of targeting is set up to make the buttons appear or disappear based on the unit's existance.
		  
			TgtTgt:
			This will attempt to perform any action on this dock on the target of the player's current target. This type of targeting is set up to make the buttons appear or disappear based on the unit's existance.
		  
			Focus:
			This will attempt to perform any action on this dock on the player's current focus.
	
			Party1 through Party4
			This will attempt to perform any action on this dock on the corresponding party member. This type of targeting is set up to make the buttons appear or disappear based on the unit's existance.
	
			P-Pet1 through P-Pet4
			This will attempt to perform any action on this dock on the corresponding party member's pet.
	
			Not in yet -
			Raid1 through Raid40
			This will attempt to perform any action on this dock on the corresponding raid member.
	
			R-Pet1 through R-Pet40
			This will attempt to perform any action on this dock on the corresponding raid member's pet.[/INDENT][/INDENT]


[COLOR=Cyan]Learning how to configuring bars -[/COLOR]

	[INDENT]First, ensure you have configuration mode ON by clicking on the minimap icon and clicking on the top-most button.

	In the past, bar/button addons just give you several rows of buttons and when you page through or perform a stance/form change, the addon was just swapping out bars. Trinity does NOT do this. EVERY bar in Trinity can actually have as many independent button group associations as each header type allows.

	With configuration mode ON, as you switch stances or pages, you may see the dock suddenly collapse and have no buttons (or if configuration mode is OFF, you will see nothing). This indicates that the associated button group does not have any buttons associated with it. This will happen on in an initial installation. Initial installs will only have associated button groups for page 1 of a paged bar and for stances or forms that are default to the class and that are not talent-based.

	One thing to keep in mind is that Blizzard only gives 120 action button ID's to easily place and use actions. Thus, Trinity only has 120 button objects to distribute amongst the potential unlimited number of bars. With an initial install, all of the buttons have already been assigned to somewhere, and if you don't count 120 buttons on your screen, it is because you are a stance class and already have buttons assigned to your other stances.

	The best thing to do upon an initial install is to slowly go through each stance/form (with configuration mode ON) to take a mental inventory of what has been initialized for you. If at one point you see a short dock with no buttons don't panic. All this means is that there are no buttons associated with the stance/page/state. What this means is you will need to steal buttons from another dock or associated button group.
	
	One thing to keep in mind is that each stance/form/paged button group can have a varied amount of buttons for the same dock. So this does not mean you have to match button counts. For example, a warrior could have 10 buttons in battle stance, 8 in defensive, and 6 in berserker, which would then free up a total of 12 buttons from those 3 groups to use with other docks or button groups.

	A word of caution: even though Trinity respects Blizzard's action ID assignments, it is still possible to get things out of whack in Trinity by removing and adding buttons excessively. It is recommended that you first take buttons from the highest numbered dock first. When Trinity assigns a button to a dock from the central pool of unused buttons, it goes sequentially, so the lowest numbered button will be assigned first. In a future version I will make it so buttons have a "home" dock and will always be chosen first to when adding regardless of it's button number.

	Now remember, other bar addons sometimes do not follow Blizzard's use of action ID's in the default user interface. So, if you are a rogue and go to stealth using Trinity and see empty buttons but had them in stealth using another bar addon, it means the other bar addon did not put your stealth abilities on the same action ID's as when you are using the default UI.

	[COLOR=Cyan]Druid stuff - [/COLOR]

	Druids have the most varied combinations a forms and can be the cause of great frustration. In WoW 2.0, Blizzard has given the ability to recognize forms that the default UI does not, like Moonkin and Tree of Life form. Because these are not standard forms, they are not populated with buttons and they are intialized empty of buttons. So when you switch to these you can have buttons specific for that form.

	I do know that some druids are unaccustomed to having these bars for these forms. However, they can be quite an advantage. For example, while in moonkin you can have just all your balance spells on the moonkin bar using the same key bindings you have in caster form that you may use for healing. In the future I most likely will be adding an option to toggle these form bars, but I highly recommend taking advantage of the flexibility Blizzard has given us in 2.0.

	[COLOR=Cyan]Priest stuff - [/COLOR]

	Both priest shadowform and spirit of redemption trigger stance changes in WoW 2.0. Because these are talents that not all priests will have, the shadowform bar or spirit of redemption bar will be populated with zero buttons upon an initial install. You must populate the bars with buttons from other button groups or docks if you wish to take advantage of this flexibility. If you do not wish to use a stance bar for either of these forms, simply deactivate the stance header and any stance buttons will be returned to storage.[/INDENT]

[COLOR=Cyan]Key binding[/COLOR]

	[INDENT]When a button is part of a header that has more than one "showstate", every button can be bound individually with individual key binds regardless of it's position on the dock. For example, the first button of each stance or form can have it's own unique binding independent of the others, or they can all have the same binding. Because of this, at first key binding can be a bit confusing.

	When you want to bind a key on a stance/paged/stealth bar and you want it to "fall through" to the other stances, you must make sure that the button's compliments in the other stances do not already have a key bind on them (The binding system starts from the left when considering buttons as compliments of each other. So if you have 12 buttons in one stance and only 7 buttons in another, the first 7 buttons of the 12 button stance will be considered the compliments of the 7 button stance, the last 5 have no compliments in the 7 button stance.)

	Now, if all the buttons that are compliments of each other have the same binding and you want to change that binding for them all quickly, the easiest way to do this is to temporarily assign the key bind to a button on a Normal bar. The reason for this is that when a key is assigned to a normal bar, the logic of the key binding system checks and clears each stance or paged bar if the bind key is the same. When you bind a normal bar button, you are saying that you want that key bind to work no matter which stance or which page you are on. 
	
	With the button and all it's compliments cleared of bindings, when you assign a key bind to any of those buttons, the key bind will then "fall through" to all the other button compliments.

	However, if a button compliment does have an active key bind, that button will not accept the key bind for a simple reason. Using the example of the 12 button / 7 button stance button group above, some people might want to have the far right button always bound to the same button, regardless of button count. So they may have both button 12 of the first group and button 7 of the second group have this same binding. First, the very fact that the "fall through" does not happen on a button with an active binding allows for having button 12 and button 7 of different groups to actually have the same binding. Second, down the road, a player may want to rearrange the 12 button group (maybe a new skill is learned or new macro created) and decides to place it on button 7 of the 12 button group. Now, if the built in protection for already bound keys didn't exist, when the player binds button 7 in the first group, the already configured group of 7 buttons would have it's binding for button 7 erased and then overridden, making more work than is needed.[/INDENT]

[COLOR=Cyan]The non-actionbar docks (bags, menu, petbar, formbar, castbar and XPbar)[/COLOR]

	[INDENT]Most of configuration buttons of these bars have the same function as the actionbar docks. Scaling, auto-hide and button configuration are the same (save for the castbar which is only limited to horizontal and vertical orientations). The one button that is unique to these type of bars is the close button (the one with the "X"). The close button allows you to hide these UI elements.

	The castbar dock and the XP dock both have +/- buttons and these work differently than the actionbar docks. These buttons will adjust the height and width of these bars.[/INDENT]
	
-------------------------------

I hope this helps some, and I will modify as I discover things I omitted :D

Maul/Osk