Yes, because you have created a brand new GDL2 object you will need to select each GDL1 object, open the settings dialogue, browse for GDL2 and CTRL+ALT (inject) the existing parameters into GDL2 to pass on the parameters.
You will have to do this one by one.
Otherwise what you could have done is 'SAVE' the object script instead of 'SAVE AS'.
This would update all your existing objects automatically with the new code.
You could now COPY the code from GDL2 and paste it back in GDL1 and then 'SAVE'.
Updating and saving the original object will affect all instances of that object in all files where the library containing that object is loaded.
So if you want to change all objects keeping there original settings then SAVE is the way to go.
You do have to be a little careful that the changes you make in the code don't break the objects.
If you add new parameters remember they won't be in the already placed instances so will use the defaults you sav in the amended object.
Something else you can look into is "Migrating" an object form one to another.
So you can have the original GDL1 migrate to the new GDL2 object.
It is possible to alter the values of new parameters in GDL2 based on values of old parameters in GDL1 or pass on the parameters as they were.
It is a bit more of an advanced GDL method so I wouldn't try to understand it unless you know what you are doing.
I don't think there is much documentation on it - I learnt by looking at the script of objects in the migration libraries.
You also need to delete GDL1 from your loaded library in order for GDL2 to automatically replace it - otherwise placed instances will just stay as they were.
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