I notice that in V2016 there is now the ability to create Detail-Callout Markers that link to detail viewports, so that if that viewport moves to a different Sheet Layer or its callout number changes, the marker responds accordingly. Great!
I can also see a tremendous need to provide a text string (hyperlink?) that does something similar, linking to a viewport or sheet layer. This way, when a sheet is added or removed from a set, matchline callouts, notes references or other embeded sheet references could respond automatically. It would allow the most flexibility as a text string hyperlink (similar to a standard interactive PDF link).
Bonus: Prior to 2016 and Project Sharing, the only way we have been able to provide a multi-user environment for a project is by creating separate project files (i.e. hardscape, planting, irrigation, details, etc.) and referencing them together with viewport references. Since we are not completely sold on Project Sharing yet due to a couple of reasons ( see other wishlist thread ) we have not yet made this transition. A way to make similar cross-references across different project files (similar to publish script?) would free up our workflow options tremendously.
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Question
ericjhberg
I notice that in V2016 there is now the ability to create Detail-Callout Markers that link to detail viewports, so that if that viewport moves to a different Sheet Layer or its callout number changes, the marker responds accordingly. Great!
I can also see a tremendous need to provide a text string (hyperlink?) that does something similar, linking to a viewport or sheet layer. This way, when a sheet is added or removed from a set, matchline callouts, notes references or other embeded sheet references could respond automatically. It would allow the most flexibility as a text string hyperlink (similar to a standard interactive PDF link).
Bonus: Prior to 2016 and Project Sharing, the only way we have been able to provide a multi-user environment for a project is by creating separate project files (i.e. hardscape, planting, irrigation, details, etc.) and referencing them together with viewport references. Since we are not completely sold on Project Sharing yet due to a couple of reasons ( see other wishlist thread ) we have not yet made this transition. A way to make similar cross-references across different project files (similar to publish script?) would free up our workflow options tremendously.
Link to comment
3 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.