Awesome Martin YOU DA MAN!! THANK YOU VERY MUCH!!! It seems writing code just comes so naturally for you. I LIKE THAT!!!
Since it seems you have already taken the time to write this do you think this could/will be incorporated into MEP? We in the electrical industry would really appreciate it. The program you wrote takes us a step closer to what M&P can do. Couple your program with some of the suggestions here along with a vision and you have a super powerhouse program that would allow you to estimate, fabricate & build just as your detailing.
I'm excited to see your program implemented. Seems you know what we are looking for, but if I could provide any insight, just let me know.
Nice Job Martin!!
With the "ConduitRunLengthAll" command, Is there any way to match the different runs to the output of the command?
For instance how do I know which conduit run is "Run: 4CF88"
When selecting the run, or a part of it, I don't see anything in properties anywhere.
Thank you Martin, your the electrcal contractors hero!
You can do something like:
Command: z ZOOM
Specify corner of window, enter a scale factor (nX or nXP), or
Select objects: (handent "121B6")
<Entity name: 7ffff77d4e0>
This is exactly what I have been looking for, except for use measuring piping runs.
Is there already a mechanism for doing that?
Can this app be altere to measure pipe and fittings?
I've made some minor modifications which should make this work for pipe, duct, and cable tray as well. The commands have been changed to simply:
Note that only length for conduit elbows are computed... duct, pipe, and cable tray runs exclude the lengths along the elbows (or other fittings such as flanges, etc., along the run).
Thank you so much.
This is definitely a timesaver.
Not to be greedy, but how hard would it be to have the output calculation return in feet?
I see someone expressed this desire earlier.
it would be fairly easy to do, assuming all users are using Imperial (just divide the result by 12)... but I wouldn't make that assumption... so it gets a little more complex to react to multiple users' preferences... i.e., most imperial users would likely want feet, but metric users would sometimes want mm, other times m (in either case, the solution is *not* dividing by 12... and therefore, is a bit more complex considering all 'types' of users).
Next on my wish list is a property set definition that gives the result of the runlength command.
Perhaps there is already a way to do this.
I would like to be able to schedule the total length of a pipe run. Is there already a prop set definition or other method to accomplish this?
Well done Martin.
Ran first time right out of the box
conduit stays highlighted after command-I regen to complete or lose highlighting...is there a better way?