Linked Document Icon

Michael_Coffee

According to the change log, 1.110, one line states: "Update recursive linked document update icons to use version icons, not link icons." Since it has been used, I don't understand why the change. There are merits for them being different, rather than the same, because if you use a version of a part within its own document, it'll use the version symbol. If the part was outside of the document, it'd use the linked symbol. While in hindsight the linked symbol would be more prevalent, there is still a difference between them. I just don't understand why the need to make them the same.

timandrews

The primary reason we decided to change the link icon to a version was to simplify the mental model for linked references. Previously, link icons were used for references that came from a different document while version icons were used for references from the same document. When we implemented the "Update all" recursive updating in assemblies and introduced the concept of pinning, we deployed a whole new set of icons to communicate the different ways an instance (or something inside an instance) could be out-of-date. The image below shows all of the different variations:



If we had kept the original model of "links for other docs" and "versions for same doc", we would have needed to create an additional 8 icons to capture all of the variations. We ultimately decided that it would be best to think about references a bit differently. A part can either reference a workspace, version, or revision. Parts that reference versions in the same document vs a different document still behave and update the same way; the main difference is that parts from the same document can be changed to reference the workspace again. To help communicate this difference, we added a tooltip when hovering over the version icon.

Michael_Coffee

Anyone have an opinion? It's been about a month.

john_mcclary

Not really, To me it doesn't matter if the object is in the current document or another document. If I see a version Icon I just understand it is a protected part. meaning it won't be updating in the current workspace.

timandrews

The primary reason we decided to change the link icon to a version was to simplify the mental model for linked references. Previously, link icons were used for references that came from a different document while version icons were used for references from the same document. When we implemented the "Update all" recursive updating in assemblies and introduced the concept of pinning, we deployed a whole new set of icons to communicate the different ways an instance (or something inside an instance) could be out-of-date. The image below shows all of the different variations:



If we had kept the original model of "links for other docs" and "versions for same doc", we would have needed to create an additional 8 icons to capture all of the variations. We ultimately decided that it would be best to think about references a bit differently. A part can either reference a workspace, version, or revision. Parts that reference versions in the same document vs a different document still behave and update the same way; the main difference is that parts from the same document can be changed to reference the workspace again. To help communicate this difference, we added a tooltip when hovering over the version icon.

Edgar_Perez

Please update the training material to be consistent with the current version of the program. For example, the slide 5 of the "Linked Document / Exercise: Using Linked Documents" is still talking about the link icon. The training material or learning pathways are great but sometimes it might create confusion when you are following along the exercises and things are little different compare with your actual screen. I agree with the update though.