Closing down the Model Sharing Change Manager takes a long time
Not version-specific
Tekla Structures
Environment
Not environment-specific
Problem: After read in, I want to close the list of model changes (Change Manager) at the bottom pane. However, this time closing the manager took much longer than usually. What could be the reason?
Answer: If more than 3 model views are open at the same time, it can cause noticeable slowness to the closing of Model Sharing Change Manager. This is because each view needs to be re-drawn separately, and depending on the model, this can take some time.
Solution: To workaround the issue, please close all the unnecessary views. You might also want to consider disabling the change manager completely or show it only during conflicting changes.
XS_SHARING_READIN_SHOW_CHANGEMANAGER
XS_SHARING_READIN_SHOW_CHANGEMANAGER_CONFLICTSONLY
Answer: If more than 3 model views are open at the same time, it can cause noticeable slowness to the closing of Model Sharing Change Manager. This is because each view needs to be re-drawn separately, and depending on the model, this can take some time.
Solution: To workaround the issue, please close all the unnecessary views. You might also want to consider disabling the change manager completely or show it only during conflicting changes.
See also
Tekla Model Sharing settingsXS_SHARING_READIN_SHOW_CHANGEMANAGER
XS_SHARING_READIN_SHOW_CHANGEMANAGER_CONFLICTSONLY