Applies to Windows 7 64 pro N5.1.1 32bit & 64bit
The behaviour outlined below does not happen when creating a new project, the global presets slot in without issue, it only happens after setting globals and then trying to open existing projects.
After setting key IDs for workspaces globally in one project, Auto Instantiate refuses to load the saved ID number for position #1, on the list of project workspaces, when opening other projects.
The default project workspace Main always overwrites the ID associated with workspace position #1,
so effectively, it’s necessary to begin numbering global presets from postion #2 - in order to avoid the first ID being overwritten when Auto Instantiate is employed.
This applies even when workspaces are locked, the Main always loads to #1 with an unlocked status by default, totally ignoring the global ruleset that Auto Instantiate should be following.
I see nothing in the manual to indicate that this behaviour is normal.