Block attributes burst
@autoskocc wrote:
.... I saw an AutoLISP from few years ago but I reckon it doesn't work with the latest version of AutoCAD.
I would not assume that. AutoLisp doesn't change much with new versions -- I have many routines that date back decades and still work. Try it, and if it doesn't work, or doesn't do what you want, write back.
Burst2 certainly doesn't keep the rest of the Block as a Block but with the Attribute parts extracted into independent Text, as I think you want. So I wonder what they could have meant by "keeping the symbols as it is after bursting."
I assume the idea suggested in my previous Message wouldn't work if there are multiple Insertions with different values assigned to the same Attributes -- I'm not sure [haven't experimented] what would happen to those Attributes [in other Insertions than the one that was Burst] once the Block is redefined without any.
Here's what I'm now imagining a routine could likely be made to do:
Find all the Blocks of that name, and put them in a selection set.
BURST the first one in the set.
Put the Previous selection [the results from BURSTing] into another selection set.
Remove the Text elements from that.
Use what remains to redefine the Block [same name].
The remaining Insertions of the original Block will still have their Attributes, even though the Block definition now doesn't include any. For each remaining Block in the initial selection set:
Insert a Block by the new definition, using the same insertion point, scales and rotation, which should overlay the original except without Attributes;
BURST the original to get its Attributes into Text objects;
Put the Previous selection into another selection set;
Remove the Text elements from that, and ERASE what remains.
Does that sound like it would do what you're after?
COMPLICATION: Would any be Inserted at scales other than 1 and/or rotations other than 0°? You would want the redefinition to be done from one at scales of 1 and rotation of 0°, so that putting new ones over old ones they would match. If different scales/rotations are involved, instead of BURSTing the first one in the initial selection, it could Insert a new one at scales of 1 and rotation of 0°, and use that for the basis of the new definition.
Would you want to find all Blocks with Attributes, of any name? Would that catch any that you don't want to BURST?
Would there be any Text elements in any Block definition(s) that are not Attributes?
I got something working when I had Blocks with all their ingredients on Layer 0, but assuming that would not always be the case, I tried to allow for other conditions, and found two problems:
1. So that the Block is not re-defined with its pieces on the Layer of the first Block it encounters [to use as the basis for a new definition without the Attributes], I had it move that Block to Layer 0 before BURSTing. But that meant that the extracted Text from its Attributes, at that one location only, are on Layer 0, but those from other Insertions are on the Layer their source Blocks had been Inserted on.
2. When I tried something with Blocks having parts on different Layers, it didn't work right. I find that BURST does not leave everything in the Previous selection when more than one Layer is involved in the Block ingredients. I'll keep thinking about it, and see if I can get into how Burst works and compensate, but so far....
@autoskocc wrote:
.... I think it might be a good start cause the attributes are bursted, they are on good layers, block is stitched together but it has an odd frame around it. ....
I assume [without trial] that if the "odd frame" is visible only when you pick on something within it, they're not stitched into a Block, but it's a Group surround [see how it lists things in the Properties palette]. If that's the case, it might not be difficult to have them made into Blocks rather than put into Groups, but under that approach it would need to be a different Block name for each one. I assume you want the same Block name & definition for all of them of the same original name, just with the Attributes pulled out -- that's what I've been trying, but with success so far only when all Block parts are on Layer 0, and all Insertions are at scales = 1 and rotation = 0 [as you described in Message 8].
