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?
Just throwing the question out here: Is it possible to write a custom script for X10 to make the program export a custom materials list with some calculated fields and some custom formatting, like a header with our logo?
If so, would anyone have an idea where I could turn to have this done for me?