You don't need to add anything after #showtooltip in order to have the macro show the icon of the ability it casts. So in the macro's case it's literally reading "cast at verh, healing touch". In your macros for example you could shorten it to One way to remember this is that stands for "at". Whenever you plan to type out "target=" you can use instead. If anyone have macros that wanna share or have Ideas to improve mine, let me know.Ī couple of pointers on how write more efficient macros: =Feral has instant heals, so this is macro for healing my partner with insta Healing Touch it will go in Bear if u are not since u probably wont using Survival Instincts if u are not under pressure = To make sure u go in form if u are not in one. = Innervate on me / if u play with someone that use mana, u can have modifier here = I like to have charges on my Shift + Mwheel up / down, so I use different macros for Cat and Bear. = This is one button Faerie Fire, you need only this one since it will change spells if you are in human or forms u can use with enrage but problem with enrage is that you lose armor, so not so good idea. Revenge is only on shred so if u realy wanna burst u go there :D = For both Mangles, Stealth still Pounce. = This is one buttton opener, you can skip this, but i like it :) if you are not in Bear or Cat it will go in cat and if ofcombat it will go in stealth. = So I made every attack I use in Cat to be in Bear the same button. = You can remove HEX from your partner arena Some are specific for my 2v2 partner so just change name and thats it. Was trying to get good macros for Feral druid on internet, but some are for different expansions and do not work in 3.3.5a. I would be glad to know what was rationale behind it and what type of work flow is proposed by Autodesk to move as fast as possible from drawing with iPart/iAssembly factory inserted with a member selected to a part factory file which can be inspected, have visibility toggled to see what is inside in this member and so on.Else // Load Rest of YUI remotely (where possible) To overcome this issue I did create a macro to jump to factory file and then. Especially if it is not I who made a project in a first place. Since names of member files are fully user configurable, it may be an unacceptable guess work to find which factory file actually controls this member. I can't see any option, which is for an example available for derived parts, to quickly open factory file from iPart member file. But when I select a specific member the drawing tree is showing the member file instead of factory file and any "open", double click and etc are causing iPart member to be opened. Selecting "active member" is asking for troubles, because "active member" is continuously toggled when I either inspect or work on iPart factory. The problem is, that when I put iPart factory on a drawing I need to select a member. This is consistent with the fact, that iPart member is considered to be fully automatically generated, so this is natural to avoid users confusion. Notice, I also cannot access properties for iPart member (no menu in content menu), I can't toggle visibility when I open iAssembly member (options grayed out), cannot do any cross section in Analyze and etc.įrom what I can see in this Inventor version any option which has a slightest chance to edit solid or assembly is disable if You open the iPart/iAssembly member. But an icon to open VBA editor is GRAYED OUT when I open iPart member, so to check it I need to open an another part.Īll macros I would like to start are in Default.ivb, so this is not the issue with VBA not seeing iPart. >(.) Do you see a 'DocumentProject' listed for that specific iPart Member document, within the Project Explorer window of your VBA Editor dialog when it is open(.) All files are having read-only attribute cleared.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |