Re: IronCAD's Approach Revisited

Feb 19, 2008 1 Replies

Rate this thread:

formatting link

> "In context design - Traditional CAD systems create what is called a
> feature tree that captures the order in which the features were
> combined to create the model. When you want to edit a feature in this
> tree all the features that occur after that point in the history are
> blanked out. Software that utilizes this approach creates a non-
> productive situation for the user because many times the feature they
> would like to reference has been removed. IronCAD does not have this
> restriction. A user can reference any visible feature on a part while
> making any required changes. This makes it both easier and faster for > the user."
>
> The reason SolidWorks still can't do this is?
>
> Jon Banquer
> San Diego,CA

cuz its not IronCAD, ffs

Now You f*ck off & die bitch...Jon the Jew don't know Hebrew HAHAHAHAHAHAHAHAHAHAHA

why because it is a different modeling tool. SWx does have sleezy features like this but they are not what i would suggest doing. and Ironcad is a boolean modeler. it uses a drag and drop interface for its modeling approach. it is quite easy to use, i could even get a salesman to use it, you might even be able to use it if you would try. but it is not a production tool that has enough features to be productive. take the detailing end of the program, it is quite lacking. the training is quite limited, just try looking at the help files, they are completely inadequate. and you John are the buzzword king, that has limited knoledge or care for what you state. and you are still loosing arguments even when you do not post one. iQ

Re: IronCAD's Approach Revisited

Join the Discussion

Didn't find your answer?