Originally Posted by NavyFC
I have two questions to try to get more out of Macaroon:
1. Why use states when you can use the built in ones? Take the example given in the OP... All states exampled are quite easily set up using the stance and prowl checkboxes from the bar menu. As I understand from the example, states are nothing more than the conditionals you would put in a macro, right? Aren't most/all of those conditionals built into the bar menu? Help me out with this one, I get a sinking feeling that I'm missing out on a very powerful part of this mod that I just don't understand (I don't understand the linking stuff either).
2. Is it possible to create a button that would change spells based on what button was pushed on another bar? How about a button that when moused over revealed the rest of the bar or revealed another bar entirely? This may be answered by answering the above question, but I want to try to get a specific answer here. I am trying to basically recreate some of the functionality of AutoBar (in an effort to trim my mod folder and memory use a bit). If I am not clear on what I am asking, let me give an example: For my Pally, I don't always want to see all the auras, but they need to be quickly available. I would like to see one aura button with the aura I last selected on it and when I mouse over that button, it shows me all of my auras and clicking one of those will activate that aura and set the original button to the new aura. The auras it revealed would have to stay up long enough for a mouse click, but disappear once one is clicked or the mouse is moved away from the area.
I hope these possibilities already exist in Macaroon. Regardless if they do or not, I absolutely love this mod as it has been an excellent upgrade to the TrinityBars heritage.
Thank you Maul and thank you in advance to the brains out there that are deciphering this puzzle for me!
|
For #1, its a matter of flexibility and combinations, heres an example of what I use on my priest:
[actionbar:1, nomod]
[actionbar:1, mod:shift]
[actionbar:1, mod:alt/ctrl]
[actionbar:2, nomod]
[actionbar:2, mod:shift]
[actionbar:2, mod:alt/ctrl]
[actionbar:3, nomod]
[actionbar:3, mod:shift]
[actionbar:3, mod:alt/ctrl]
then I create 3 buttons with:
/itemrack EquipSet (Healing/PVP/DPS)
/changeactionbar (1/2/3)
and disable changing actionbars via the mouse wheel (so it doesnt get accidentally changed in combat). These states go into every bar I make except a few generic ones for professions/quest items/etc and make it so I have 3 custom states for my bars, one for each set of gear I use for various tasks. When I click one of my 3 state change buttons I immediately go into that gear set (OOC, in combat it just changes weapons) and have all the buttons I need for that task placed as I like them (so, instead of Alt/Ctrl+4 for fear on my healing bars, it moves to E on my PVP bars - much easier to access for when I need it most).
If your a warrior or druid or any class that has real stances, you can do something like this:
[stance:1, nomod]
[stance:1, mod:shift]
[stance:1, mod:alt/ctrl]
[stance:2, nomod]
[stance:2, mod:shift]
[stance:2, mod:alt/ctrl]
[stance:3, nomod]
[stance:3, mod:shift]
[stance:3, mod:alt/ctrl]
etc, for fully customizable bars in each stance, better yet, if you find you want your shift button to have its own bar independent of stance change it to this:
[mod:shift]
[stance:1, nomod]
[stance:1, mod:alt/ctrl]
[stance:2, nomod]
[stance:2, mod:alt/ctrl]
[stance:3, nomod]
[stance:3, mod:alt/ctrl]
and if you want to get really damn crazy you can do this and have each stance have not only its own shift/ctrl/alt bars, but also 6 fully functional actionbar pages to use:
[stance:1, actionbar:1, nomod]
[stance:1, actionbar:2, nomod]
[stance:1, actionbar:3, nomod]
[stance:1, actionbar:4, nomod]
[stance:1, actionbar:5, nomod]
[stance:1, actionbar:6, nomod]
[stance:1, actionbar:1, mod:shift]
[stance:1, actionbar:2, mod:shift]
[stance:1, actionbar:3, mod:shift]
[stance:1, actionbar:4, mod:shift]
[stance:1, actionbar:5, mod:shift]
[stance:1, actionbar:6, mod:shift]
[stance:1, actionbar:1, mod:ctrl/alt]
[stance:1, actionbar:2, mod:ctrl/alt]
[stance:1, actionbar:3, mod:ctrl/alt]
[stance:1, actionbar:4, mod:ctrl/alt]
[stance:1, actionbar:5, mod:ctrl/alt]
[stance:1, actionbar:6, mod:ctrl/alt]
[stance:2, actionbar:1, nomod]
[stance:2, actionbar:2, nomod]
[stance:2, actionbar:3, nomod]
[stance:2, actionbar:4, nomod]
[stance:2, actionbar:5, nomod]
[stance:2, actionbar:6, nomod]
[stance:2, actionbar:1, mod:shift]
[stance:2, actionbar:2, mod:shift]
[stance:2, actionbar:3, mod:shift]
[stance:2, actionbar:4, mod:shift]
[stance:2, actionbar:5, mod:shift]
[stance:2, actionbar:6, mod:shift]
[stance:2, actionbar:1, mod:ctrl/alt]
[stance:2, actionbar:2, mod:ctrl/alt]
[stance:2, actionbar:3, mod:ctrl/alt]
[stance:2, actionbar:4, mod:ctrl/alt]
[stance:2, actionbar:5, mod:ctrl/alt]
[stance:2, actionbar:6, mod:ctrl/alt]
[stance:3, actionbar:1, nomod]
[stance:3, actionbar:2, nomod]
[stance:3, actionbar:3, nomod]
[stance:3, actionbar:4, nomod]
[stance:3, actionbar:5, nomod]
[stance:3, actionbar:6, nomod]
[stance:3, actionbar:1, mod:shift]
[stance:3, actionbar:2, mod:shift]
[stance:3, actionbar:3, mod:shift]
[stance:3, actionbar:4, mod:shift]
[stance:3, actionbar:5, mod:shift]
[stance:3, actionbar:6, mod:shift]
[stance:3, actionbar:1, mod:ctrl/alt]
[stance:3, actionbar:2, mod:ctrl/alt]
[stance:3, actionbar:3, mod:ctrl/alt]
[stance:3, actionbar:4, mod:ctrl/alt]
[stance:3, actionbar:5, mod:ctrl/alt]
[stance:3, actionbar:6, mod:ctrl/alt]
If you ever need that, you have too many buttons :P
(note: I use ctrl and alt as the same bar, but you can break them up if you want, "/" is used for a logical "or" so you can have any combinations of values if you use / to seperate them). The checkboxes allow users not comfortable with macros to get a lot of the functionality (maybe all, when combined with linking) out of macaroon without actually having to know all the stuff above, but if you have a moderate grasp of macro commands you can tell macaroon exactly what you want it to do via custom states and skip the other check boxes entirely if you so wish (excepting things like autohide which only control the look of the bar, not its actions). Sometimes you wont need the flexibility of custom states and you can use the check boxes to save time/effort, but you could not do any of the above examples with the check boxes alone.
as to #2, I believe this is what Maul means when he talks about anchor bars, which are not yet implemented. I cant say for sure however. Changing spells based on what was pushed on another bar might have to be done via a trick like what I use for actionbar pages, but the rest sounds like anchor bars.