You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This feels like a bug - was definitely a surprising discovery. Firstly, I was surprised that ComponentDefinition#save_as modifies the guid until I realized that it changes the path associated with the component. OK fine, I guess this makes some sense.
But why would calling save_copy also change the guid? (But only for components that have an associated path set)
SketchUp 2024 24.0.579 Windows
To reproduce, select a component (eg. Teddy) in the model using the Select Tool. Then run:
Both of these sounds like bugs to me.
Saving out the component does change the Loaded From Path but it doesn't
make it a separate revision of the same component. Pasting the component
from the clipboard or dragging it in from the folder should not create
another "#1" version of the component.
This feels like a bug - was definitely a surprising discovery. Firstly, I was surprised that ComponentDefinition#save_as modifies the guid until I realized that it changes the path associated with the component. OK fine, I guess this makes some sense.
But why would calling save_copy also change the guid? (But only for components that have an associated path set)
SketchUp 2024 24.0.579 Windows
To reproduce, select a component (eg. Teddy) in the model using the Select Tool. Then run:
If you run the above snippet when selecting a component with no associated path, the guid will NOT change.
The text was updated successfully, but these errors were encountered: