Hi Alex,
The edge selection that you did, let’s say of a cube, would create twelve single entries in this Selection Tag for the twelve edges. After ‘fracturing’ the cube these twelve edges do not exist anymore, as each junk is generated newly, and no new selection tag is produced.
The options for Selections of the Voronoi are limited to six different kinds, see Attribute Manager Selection tab. Those are generated tags for the Voronoi object, as it keeps all “chunks” inside of one Generator. The selection made to the cube (12) would be multiplied many times. Once it is is made editable, only those six variations are applied to each chunk. Nothing from previous selection of the “source object” are inherited.
So after trying to create a “old-edge” selection, I placed the successful result of that back to the Voronoi Object and the selection is ignored.
(I made the Voronoi editable. Then “Connect and Delete” to get one object back so I could define a Selection for a Generated object - as it contains all. The idea was to use the generated selections and after selecting the unwanted parts, I used Selection>Hide Selected. So I was left with the original edges after a while. I was able to only select the wanted edges. But this Selection tag was not compatible with the Voronoi Object.
After that I use the Fracture object for the “Connect and Deleted One”, but once it was in the Fracture Object, the same problem happens, all was newly generated and the Selection was ignored.
My only idea is make Suggestion to MAXON about your needs, but I guess it will be too late for an implementation.
I tried more, e.g., VAMP to transfer data, in case you have the same idea, but it failed as well, badly to be honest.
If you can illuminate me more what the target is, perhaps that pushes a new idea…
All the best