@dale as i understand there’s no other way than scripting to get import/export block functionality? Only handling on own read/write File3dm will do the work? No shortcuts?
I’m digging whole morning to find a way to export individual block and import 3dm file as embedded and linked block directly from code.
Even via script i noticed different behavior in v5 and v6 - v5 on double import of the same file in a row keeps block name the same - v6 changes definition adding uuid/guid to its name?
Besides after deleting linked block if there is a block in it will stay there no matter if i delete it or even purge whole file referenced block seems to be “stuck” if done multiple times v5 dobules them with XX ( where X is an appropriate number) “postfix” while v6 seems not doing this. I’m wondering how uuid/guid of instance def behaves when saved and reopened is it reliable value to work with when we talk about linked blocks?
Also no opt to reexport already linked block via BlockManager scripting (even not working in modal) - i guess only copy approach will work here deciding using - InstanceDefinitionUpdateType - but how do i track path of original archive - is it SourceArchive ?
Next weird thing in v6 is this:
Compact doesn’t make a difference here + Purge hides this temporarly then - boom again big list:
Besides deleted linked blocks with reference layers leave “unactive” mess in layer manager and can’t be deleted at all. Seems like the block management system has “holes larger than a Swiss cheese”.