Flanges, somebody talking my language. Deal with flanges all day long. And yes I have this problem all day long as well. My answer is what you thought all along, I cheat. Copy the part to be subtracted a known distance and subtract the remaining one from one solid, then move the other back by that known distance and subtract it from the other solid. Hopefully, someone else will come along and help us both out. GL
(DEFUN C:SLC2 ()
(COMMAND "CMDECHO" "1")
(command "osnapcoord" "1")
(SSGET)
(setq pta (getpoint "\n Select First Point On Slicing Plane: "))
(setq ptb (getpoint "\n Select Second Point On Slicing Plane: "))
(COMMAND ".SLICE" "P" "" pta ptb "@0,0,12")
)
(DEFUN C:SLCY ()
(COMMAND "CMDECHO" "1")
(SSGET)
(COMMAND ".SLICE" "P" "" "ZX")
)
(DEFUN C:SLCX ()
(COMMAND "CMDECHO" "1")
(SSGET)
(COMMAND ".SLICE" "P" "" "YZ")
)
(DEFUN C:SLCZ ()
(COMMAND "CMDECHO" "1")
(SSGET)
(COMMAND ".SLICE" "P" "" "XY")
)
These used in conjunction with point filters, ucs, osnap, etc. accomplish our desired results.
No not really, we don't do a lot of editting of the primatives anymore. Nearly everything we do is a block or produced parametrically. Stuff like pipe flanges, valves, fittings, etc are blocks (or are created parametrically and then blocked) that we insert through an in-house pipe router routine, as is the steel, concrete, plumbing, electrical conduit and cable tray. Every now and then we need a custom bracket or an odd piece of mechanical equipment that we haven't already cataloged, so one of us will have to bang it together out of the primatives. But that's happening less and less often.
Yeah, when they're watching anyway. We also do fabrication, manufacture, construction. We go from concept to completion, heck we'll even run it for you after it's built.
>> i'm the only one who works on it or even sees it before it goes to floor, i dont even get my prints checked, so i have to be very careful bout wiping my own. <<
I did that for a while in the mid 80's, it was kinda fun, but I never really could relax until they got done with whatever it was.
We're just one subsidiary of a large wold-wide organization, so I get to see a multitude of different design challenges.
I've mentioned this before that we had tutorials of Inventor and SolidWorks at the same time. Inventor crashed all the time and we own SolidWorks today. And believe me when I say, I wanted Inventor to be the chosen one, but alas...it must work first. I keep looking in on their NG and see lots of problems that I think should be fixed by now. ...Someday, probably after I'm retired. Right around the corner ;-)
Reply From: JDMATHER
Date: Apr/15/04 - 13:19 (CDT)
Re: Subtract without unioning?
How about you?
I used to copy in place, but I'm really a visual guy and I like being able to see what I'm doing a little more. Copying out and moving back really isn't much of a big deal, time wise or otherwise. Then I spend a couple of seconds more highlighting just as a visual check.
And you are right to check on a lisp already written for it. Later
But the high-tech companies decided to quit building so much a couple years
ago when the economy took a big dump, so now I am doing mostly civil,
environmental, and DOT. Mixin' it up.
"OLD-CADaver" <nos...@address.withheld> wrote in message
news:1197320.1082143014317.JavaMail.jive@jiveforum2...
Thanks
--
Alan
Nice guy. The result is that our software's are not really all that
compatible. He implements a process that keeps track of the edits to solids,
so that they can be altered and/or undone. We simply change the solids as
need be, without using the standard Boolean operations that his software
tracks so that it can work. We can modify any solids created with his
software, but his software would loose the ability to update later. His
stuff is more geared towards design-engineering and is more powerful for
more things in that area and ours is geared more towards
design-to-manufacturing and BOM. You could theoretically use both or one or
neither. It all depends on what you want to get done.