Fence tool question. Custom fence style bringing ALL classes from original file.

[hollister design Studio]

I just noticed that all of my custom 'Fence Styles' bring all the classes of the creation file into the new file.

Stock fence styles don't do this.

Any idea what I did wrong in saving these styles?

 

Video:

• create blank doc - this creates two default classes
• create unstyled fence - this creates two new classes
• 'Replace' with a stock fence style - this uses the same two classes as an unstyled fence.
• "replace' with my custom fence style - This added ALL the classes from the creation file. 

 

Why?

 

•  

   

 

Also, I can't purge these classes. There are zero unused classes available to purge.

I can delete them, but VW wants to reassign to a different class first.

 

What is going on?

 

[hollister design Studio]

@Katarina Ollikainen

I just rewatched your amazing coffee break on the new fence tool - Wondering if you could take a look?

[hollister design Studio]

OK - I figured it out!

 

There is a problem with the "send to surface" option in the fence style editing menu.

If you enable this option on the "General" tab and select any classes in the "apply send to surface by class" menu, those classes will be included in your symbol definition.

It also prevents you from purging any of these classes - even if there is nothing on them!

This can mess up your class structure and cause confusion.

 

To avoid this, you should make "send to surface" a 'by instance' attribute and leave it unchecked in your symbol definition.

You have to then check it if you want to use the 'Gravity' feature once it's imported into your new file.

 

I just went back and edited all my saved fence symbols, and this seems to work.

 

 

 

Here is a screen grab:

Edited February 28 by hollister design Studio

[Katarina Ollikainen]

@hollister design Studio, I'll file a jira on this straight away so we can look at the effects. Thank you for highlighting this.

The idea is for the style to save information about classes you don't want the send to surface to work on (that you have manually unchecked) to avoid the need to do this process for every project (if you don't want a fence to listen to a specific class in project A, then you probably don't want it to listen to it in project B either). This is the effect I get when testing it.

However, I'll see if we can avoid creating the classes in the new document until they're created/used outside the fence style.

I'll let you know when I have some more info.

[hollister design Studio]

 

1 hour ago, Katarina Ollikainen said:

...The idea is for the style to save information about classes you don't want the send to surface to work on...

I figured something like that.

And if it only brought in  the checked classes that would be fine.

But it brings all of them into the new doc, which is not a good idea.

 

I noticed because The document I had created these fence styles in had been imported from Autocad - so it had telltales like class '0' and class 'nonplot' (which I would never purposefully create!). It also had a lot of 'A-'  classes like walls, fixtures, sinks, and mouldings that as a landscape designer I hardly ever need.

 

1 hour ago, Katarina Ollikainen said:

...I'll see if we can avoid creating the classes in the new document until they're created/used outside the fence style...

 

This would be helpful, or at least some documentation that it does this so users aren't caught like I was.

 

 

Finally, my work around of making that attribute 'by instance' and keeping it unchecked in the saved Fence Style works for now.

easy enough to check it after the style is imported.

 

 

Thanks for reaching out!