MLCad ~movedto buggy???


Re: MLCad ~movedto buggy???
#25
I don't understand Magnus point ether, his above picture proves MLCad doesn't apply the 132-old.dat transformation as it should when doing an upgrade.

It's clearly just replacing the .dat reference while keeping the original transformation.

There are no old and or new parts there are only transformations. If you put an ~moved part in a new model it should only affect the BOM before and after the upgrade while visually remaining the same as the moved to transformation tells the parse (like any other reference) how to bring the target part into the local space of the current file.
Reply
« Next Oldest | Next Newest »



Messages In This Thread
Re: MLCad ~movedto buggy??? - by Stephen - 2015-05-06, 10:48
Re: MLCad ~movedto buggy??? - by Stephen - 2015-05-06, 12:03
Re: MLCad ~movedto buggy??? - by Stephen - 2015-05-06, 13:36
Re: MLCad ~movedto buggy??? - by Stephen - 2015-05-06, 14:56
Re: MLCad ~movedto buggy??? - by Stephen - 2015-05-06, 15:46
Re: MLCad ~movedto buggy??? - by Stephen - 2015-05-07, 7:58
Re: MLCad ~movedto buggy??? - by Stephen - 2015-05-07, 8:46
Re: MLCad ~movedto buggy??? - by Stephen - 2015-05-09, 12:46
Re: MLCad ~movedto buggy??? - by Chris Dee - 2015-05-09, 16:52
Re: MLCad ~movedto buggy??? - by Steffen - 2015-05-09, 19:13
Re: MLCad ~movedto buggy??? - by Roland Melkert - 2015-05-11, 17:46

Forum Jump:


Users browsing this thread: 2 Guest(s)