Block Insert (BI) is the preferred method to add new instances of a Block.
Meaning you need to fill in the Attribute values from scratch or use the default, but there are other ways that clone an existent set.
Now before anyone starts asking why not using BI:
All Blocks and Attributes are queried by a script for this: https://www.qcad.org/rsforum/viewtopic.php?f=30&t=9878
I am merely investigating if there is a difference in how these entities are created.
For those who want to know: The queried id's are at random, Block Reference don't point to child's but Block Attributes point to parents.
Figuring out what belongs to which Block Reference seems to be harder than expected.
Anyway, that is for the Script Programming and Contributing forum ...
What works well:
All these 3 methods: Copy / Paste .. Copy with reference / Paste .. Move / Copy with n copies
clone the original Block Reference with Block Attributes as a whole new set.
Where the issue is:
Duplicate (DP) doesn't keep the set together, the newly created Block Attributes refer to the original Block Reference and not to the clone.
Rather similar as if we use the other 3 mentioned methods on a Block Attribute only, without selecting the Block Reference itself.
Then it is probably intended behavior ... There is no newly created Block Reference to associate with, to set as parent.
Selecting only a Block Attribute is possible if that is preferred by App.Prefs.
Selecting a Block Reference with Attributes always selects it with the associated Block Attributes together.
Only, cloning just a Block Attribute is also erogenous ... Which of the two Attributes will be displayed in the Property Editor?
In the example file I cloned the first column with the mentioned methods.
When selecting Block Reference A then all 5 Block Attributes will be selected, the 2 original and the 3 duplicated.
- The listed Block Attributes in the Property Editor is a mix of things: The ID is that of clone B, the Type is that of clone C.
Selecting Block Reference B will not select any Block Attributes, although it is based on Block 'NosyItem' what has 2 Block Attributes.
What happens if you select a Block Attributes depends on your Application Preferences.
Synchronize Attributes (UY) can worsen things.
- With nothing selected, clone B receives 2 new empty Block Attributes, empty is correct because there is no default value defined.
- Encountered that cloned Block Attributes are relocated, some do but not all.
Everything depends on if the file was saved and reloaded or what is selected or if other entities were added ...
... Not really sure, it seems not that easy to replicate this behavior.
- Associations may differ afterwards.
So, maybe:
- DP clones things incorrectly ... A bug.
- It should be prohibited to clone a Block Attribute on its own in any way.
- Block References should point to their Block Attributes.
instead of that (too) many Block Attributes point to their parent Block Reference ...
Regards,
CVH
