 | | Re: MLCAD rotation (future request)
|
| I like this idea of storing the rotation data. But I wouldn't restrict it to mpd but store it in any dat file ... This allows having different rotation points per sub-model. I will forsee something like the statement suggested from Sproaticus (...) (24 years ago, 16-Aug-00, to lugnet.cad.mlcad)
| | | | | Re: MLCAD rotation (future request)
|
| (...) Cool! :-, (...) (Also answering Steve's post) Nah, I wasn't thinking of restricting it to a sub-file only, but rather to have the option of doing so. In fact, for simple one-off models (which the majority of mine are, anyway), it would be best (...) (24 years ago, 16-Aug-00, to lugnet.cad.mlcad)
| | | | | Re: MLCAD rotation (future request)
|
| (...) But an include function is different from a subfile function. Basically, anything in a subfile is scoped to that subfile, and doesn't exist outside of the subfile. Yet another reason for a 0 INCLUDE (or 0 MACRO) meta-statement. Steve (24 years ago, 17-Aug-00, to lugnet.cad.mlcad)
| | | | | Re: MLCAD rotation (future request)
|
| Steve Bliss wrote... (...) If you by "subfile" mean an MPD subfile, I think the scope is public, see the thread (URL) (24 years ago, 17-Aug-00, to lugnet.cad.mlcad)
| |
