To much work to get back to original scale, in fact likely out of sync anyway. Its a good idea to either work to the grey values or scale definition after forcing a size change with an attribute value not the same as the grey one. Groups become unstable when out of sync,
Keep in mind that the size changes are actually scale changes, so a surface stretches or shrinks, one can use Tig’s scale method or others to reset the surface.
Single level DCs can retain their name without automatic uniqueness. They can be retained in a working DC that references the parent. To save writing the same for each new cupboard type this can be inserted, The initial disposable wrapper is required to protect from overriding position and rotation values on insertion from an outside source
This shows the reload, replace and swap. Reload can change in a global context regardless of location any component with the same name (path?) this does not include unique ones. (hence the simple one level types) where as replace can only work in the same context and swap one at a time.
By far the best idea is Dan’s with extensions that require minimum input from the user
these are the component files:
HANDLE WRAPPER.skp (208.1 KB)
Handle.skp (191.6 KB)
Modern_Curved_Metal_Bar_Cabinet_Pull_JSB.skp (43.2 KB)