Moonlight wrote:
But would loading and upload the library part from the project would reset it ??
So you have many instances of ‘object 1’ in your job.
They are all the same object but may have different parameter settings.
They all have the same GUID.
You create ‘object 2’ which has a new GUID.
This object contains the migration script that looks for the old GUID and then swaps it to the new GUID.
It can also set the values of any parameters so you can adjust existing parameter values or set new ones.
This migration script will only take effect object with the original GUID is missing from the loaded library, which is why you must delete it from your library (this includes the embedded library).
If it is still in there it will just load as normal and nothing will happen.
If it is missing, the migration script of the new object detects the missing objects and replaces them with the new one (and resets parameter values if you scripted that - new parameters will just take on the default values of the new object, but again you can define those as well if you want).
Barry.
One of the forum moderators.
Versions 6.5 to 27
i7-10700 @ 2.9Ghz, 32GB ram, GeForce RTX 2060 (6GB), Windows 10
Lenovo Thinkpad - i7-1270P 2.20 GHz, 32GB RAM, Nvidia T550, Windows 11