Most OnlineNewest Member
In X12 I've noticed that when using Structural Member Reporting in a material list, the price column in the list does not appear to be sensitive to whether a "per unit" or "per length" calculation is being performed by the material list. In both cases, the material list appears to use the same Price variable in the Component Panel of each object. Does anyone know of some Ruby scripting that could be used to correct this? Off hand, I'm thinking of a macro inserted into the Price variable on the Component Panel of each structural member that would use the Material List row context to report a price that depends on how the row wants to use the Price.
OK, so today I learned that Legacy is just a fancy term for obsolete. See, I do know how to search
I have numerous macros, from others and some I wrote. Has there been any enhanced documentation regarding what "migrating" is going to do to my macros and what I can expect? Or how to fix issues? Is this going to put the brakes on my workflow? I know enough to write small macros for menial tasks, but I do not have an extended knowledge.
Or is this just not a big deal?
I apologize because I know this topic has been covered many times but I can't seem to find exactly the help I need from previous posts.
I have created a simple room information label but wanted to modify it slightly. See attached. Want ceiling height to read in feet and inches and want to round the room volume to nearest whole number.
A related matter is when I go in the text box and try to insert a user defined macro they are all grayed out. I was attempting to copy and modify the volume macro to round out, but could not insert the modified version.... Not sure why that is.
If someone can point me in the right direction and or provide any assistance, that is greatly appreciated.
Thank you, Mike Dolce, Architect
The Andersen 100 Series windows [Fiberex] are always popular with a builders. Primarily, they offer different interior and exterior colors, not as ugly as some other Vinyl... Sometimes designer want to know if he is using standard vs custom sizes [adds +$$].
So here is a validator macro, that can be assigned as a label or just executed in the tmm
Free Macro, enjoy
Code demonstrate use of Ruby arrays, and "any?" method.
I also have A200,400, and pella.. But this will get you started if you are not 100% familiar with Ruby.
I do renovation work frequently. As part of my process I load a PDF of the existing plan then trace over it. I would love to have a button on my main toolbar that would toggle that one layers visibility. It is a pain to click through the layer dialog many times a day for this. Any thoughts?