triplus wrote: ↑
Wed May 08, 2019 7:06 pm
I assume the Link effort does all the heavy lifting in the background? Documents stay partially or fully loaded/opened in the background, on the external document tab close? How does "force closing" the external document affect the assembly document? What changes? Assembly document likely still keeps everything it needs (partially) loaded? If that is how it behaves, why not making the final step and to make that a default behavior?
If you force close the document, the linked part geometry in the assembly will disappear, and you'll get exclamation marks on those broken links if you recompute the assembly document. The user can, say, rename the external file, and copy another one over, maybe from backup, and then manually open that new file. If the file has the same path and name, and contains objects with the same name, then the assembly will auto fix all the broken links. If not, then you can still manually fix those links by drag and drop the corresponding objects in the new file into the assembly.
This reads as if all of that is already the default behavior? Partially loaded document will still load linked feature history, but if "freeze" is used on the feature it gets loaded without history? Is "freeze" (core) Link effort related feature?
Partial loading is auto activated if there are independent objects in the external document, and the assembly only links to some of them. Say, you have a document with all kinds of screws, and the assembly just used a few, then those unused ones will not be loaded. This can be done automatically only if the objects have no dependency between them. Some objects, on the other hand, can function even when their dependents are not loaded. But this cannot be done automatically, because the object must implement its own logic to deal with partial loading situation, where its link properties are not fully restored. Normal object will surely report it as error. This is why 'Link' cannot provide default 'Freeze' feature, because it does not know how the linked object works, or in another words, what information to store in case the linked object is not loaded. My assembly container is one example that implements this 'Freeze' feature. The other one is the SubShapeBinder from PartDesign.
triplus wrote: ↑
Wed May 08, 2019 9:05 pm
realthunder wrote: ↑
Fri May 03, 2019 11:38 pm
BTW, one major difference of asm3 and asm2 is that the part/sub-assembly hierarchy is integrated into the upper assembly. You can directly edit any feature inside the main assembly without explicitly switching to the part document tab view.
Including editing a Sketch from such Part in Assembly document? If yes, being able to use Assembly geometry as an external geometry reference in such Sketch?
Yes, you can edit the sketch at the linked placement, or in-place, so to speak. Right now, sketch cannot use external geometry from linked document. You cannot event use external geometry from a different body in the same document. You'll have to use things like shape binder to bring in the shape. The binder takes care of the complexity of cross coordinate system transformation. In the future, I may try to copy that logic into sketch object so it can be handled directly.