Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.

First time visiting? Here are some places to start:
  1. Looking for a certain topic? Check out the categories filter or use Search (upper right).
  2. Need support? Ask a question to our Community Support category.
  3. Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
  4. Be respectful, on topic and if you see a problem, Flag it.

If you would like to contact our Community Manager personally, feel free to send a private message or an email.

option to import current version of standard library to improve regeneration times

monroe_weber_shirkmonroe_weber_shirk Member Posts: 96 EDU
edited March 2021 in Product Feedback
Complex designs that involve feature script in multiple files have slow performance when different versions of the standard library are used. The version of the standard library is set in each featurescript. Given the normal progression of coding this results in different versions in each file and thus slow performance. 

Solution:
Add an option to set the version of imports at the top of a featurescript to be to the current version. This would extend the concept of "current workspace" across files and would eliminate the need to manage the version of these import statements across dozens of files and featurscripts. This would be identical to the approach used for parts that are derived within the same workspace where the user can select to derive a part of either a specific version or of the current workspace.

Comments

  • romeograhamromeograham Member, csevp Posts: 676 PRO
    @monroe_weber_shirk
    Don't forget to vote for your own IR!
  • lougallolougallo Member, Moderator, Onshape Employees, Developers, csevp Posts: 2,005
    @monroe_weber_shirk I want to try to get a bit more info here.  In order to use FS outside of the current document, it would be saved in a version.  Are you simply asking to be able to say, always give me the latest version of this FS import all the time? 
    Lou Gallo / PD/UX - Support - Community / Onshape, Inc.
  • monroe_weber_shirkmonroe_weber_shirk Member Posts: 96 EDU
    Yes. The standard library import would have an option to always use the current version. That would eliminate the need to change this import in each document within a workspace. Whenever a new version of a workspace is created it would be using the latest version of the standard library.
  • lougallolougallo Member, Moderator, Onshape Employees, Developers, csevp Posts: 2,005
    There are a few issues with having the STD library "pinned" to the current version in a workspace today.  One is that the pinning of this will spontaneously break every feature added to any part studios in that workspace if there is an issue.  One of our philosophies is to never do anything to break parts if the user is not actively asking for an update.  What should happen is if you are on the version behind the current one, we should show you an update (like linked documents do) for the standard library.  This way you have to still update it but it is 1-2 clicks and an explicit action.
    Lou Gallo / PD/UX - Support - Community / Onshape, Inc.
Sign In or Register to comment.