Hi Tim - I traded a couple emails with Autodesk staff on this. My understanding (not a developer) is this is not merely something they overlooked. Consider when a 2020 file is opened in 2020.2 it is not going through an upgrade because the file format is compatible. This creates a scenario where they are not activating upgrade code to resolve the existing file's structure with a new version's structure.
Unfortunately this new subcategory gets enabled and its visible status is "on" at the outset. It's my understanding that "off" isn't an option...in this scenario...without also creating an upgrade scenario...which is conceptually a no-go...within a release year.
Upgraded files go through an upgrade process which imposes rules on that process...which includes a task that deliberately "turns off" this new subcategory. It's a quirk of the file open sequence/process.
I think they didn't expect it to be a significant issue. It doesn't print after all. It can negatively affect zooming behavior in many views though. User perceptions can't be ignored either. An unexpected "thing" encroaching on views is "bad"...similar to seeing a view's crop boundary when not intended.
To their credit, they asked if I agreed they should create a Dynamo solution to turn it off in all views. Naturally I encouraged them to DO IT! Hopefully we'll be able to say that such a solution exists soon.
Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
