Is there a way to not delete template blocks when doing purge?

VisualARQ
1

Hello everyone, I won’t to know if it has a way or work around - that is not placing all blocks in the file; to do purge and select to purge blocks but leave the visualarq blocks intact.

If this isn’t possible yet, please consider implementing this feature.

2

purge only purges unused blocks. if you dont want to purge them, put those blocks onto a layer and hide them or script a custom purge command via an llm of your liking

I am not sure what you mean with visualarq blocks intact - visualarq blocks are somewhat predefined grasshopper styles that won‘t vanish after a purge.

3

Well, you can also have some VA definitions (doors, windows) using blocks. So, they shouldn’t be purged even if there are no instances of these blocks in a model. I think so. But they get purged… With lots of such definitions it’s a pain to get them back. The workaround is to write definitions to a library, it keeps info about blocks. I use external blocks, embedded and linked, and this works.

Cheers, Jaro

4

yes they do if you use a template with a lot of furniture for example but doesn’t use them (don’t put them on the geometry space) they willvanish, but it will still remain on the VA tamplate the name of the furniture, but without the block geometry. And I gave the furniture example because it can be made from a static block and not a necessarily a GH script.

5

yes, but this is the problem, because if I load the library/template and then after it I hit purge with blocks definitions, what happens is that if I load the library again, it wont substitute the previous definitions because its was already loaded in the past.

6

Hi @Leo13,

Thanks for reporting this. The “Purge” command shouldn’t remove objects (like block definitions, annotation styles, etc.) that are in use by VisualARQ styles.

It worked fine in earlier versions of Rhino 8, but a recent update broke it. I’ve fixed the issue in VisualARQ 3.10 RC2, which will be released on April 15th.

I’ve also confirmed that this problem doesn’t occur in VisualARQ for Rhino 7.

Enric

7

Many Thanks! This problem is super annoying

8

I have just checked. Loading a VA library restores purged blocks. If they were parts of VA definitions and got purged somehow and have gone, after the import these are back and properly displayed.

Cheers, Jaro