The removal of baseCS is already rearing its ugly head.
If I want to recover a file or simply start a new one, I typically copy > paste from a gct backup. Problem is, now baseCS is removed unless the user does one of two - and only two - very specific actions, it doesn't exist, meaning the pasted script wont execute as it cant find baseCS. Sure, the simple answer is, add baseCS then paste in the code, but really this is an example of potentially many problems that this new functionality will cause.
When this idea was first proposed I mentioned the problems it will create, particularly for new users. Most simply wont be able to fathom how to do anything with the software and will probably jump into the arms of Grasshopper which doesn't have such idiosyncratic nuances.
Can there not be a tick box in the Workspace > Preferences that gives the user the ability to decide if baseCS is automatically created or not?
As much as the missing baseCS may disrupt a copy/paste workflow from pre-Ss6 GC scripts, the non-interference with non-GC project files was the overriding concern for the removal of the automatic baseCS insertion when opening a DGN file with GC.
We will consider your suggestion of a GC preference to insert a baseCS into any DGN that is accessed with GC and does not contain a CoordinateSystem.AtModelOrigin, yet.
The work around is definitely to keep a text file (or GCT file) that contains the transaction of adding a baseCS:
transaction modelChange 'Add baseCS' { node User.Objects.baseCS Bentley.GC.NodeTypes.CoordinateSystem { Technique = 'AtModelOrigin'; DGNModelName = 'Design Model'; SymbolSize = 1; GraphLocation = <auto> {40.0, 40.0}; } }
https://communities.bentley.com/cfs-file/__key/communityserver-discussions-components-files/360/baseCS.gct
Answer Verified By: Mueller