Fill region vs Detail component parameters

[yes_and_no]

(A) We use filled region for many things, they helps with area calculation, etc. with less interfering with the model.

As a result, the detail component, mostly also filled regions, when loaded into project will inherit all the parameters of filled regions in the project, which is confusing, specially when you look at the property browser.

Is there a better choice than filled region as said in (A).

Anyone ?

[David_W_Koch]

Have you tried using Areas (in an Area Plan) for plan area calculations?

[barthbradley]

Why don't you name the Fill Pattern in the Family differently/uniquely from the Fill Patterns in the Project?  That way it will be unaffected in the Project .  

Additionally, did you know you can associate the Fill Pattern to a Family Types Parameter? This will allow you to change the Fill Pattern of the Family's Filled Region to a different Fill Pattern inside the Project environment. 

[yes_and_no]

I love your idea very much and put that into a test right away. Made a brand new detail component family, filled region named "barthtest", loaded into project and bum, it s not working, it still inherits all other parameters (which is a lot, that s why they bother me).

[barthbradley]

What do you mean it "inherits all other parameters"? What parameters? 

[ToanDN]

---

@yes_and_no wrote:

(A) We use filled region for many things, they helps with area calculation, etc. with less interfering with the model.

As a result, the detail component, mostly also filled regions, when loaded into project will inherit all the parameters of filled regions in the project, which is confusing, specially when you look at the property browser.

Is there a better choice than filled region as said in (A).

Anyone ?

---

For plan area calculations you can create use Area like @David_W_Koch suggested.  They do not interfere with the model and you can have multiple calculations for different purposes using different Area schemes.

For elevation calculations then you can use filled regions if you don't want to model with a higher LOD.  I wouldn't use families because they are not flexible (shapes and sizes).

[yes_and_no]

Problems are not with project filled regions.

Problems are with small detail components that will inherit all of project filled region parameters when loaded (as when we working on details). Text parameters for example (about 8-10, for scheduling purposes).

We use filled region both in plan and elevation, so a half-half solution won't solve the problem.

We don't mind the area calculated parameters, which are just only a few.

[ToanDN]

---

@yes_and_no wrote:

Problems are not with project filled regions.

Problems are with small detail components that will inherit all of project filled region parameters when loaded (as when we working on details). Text parameters for example (about 8-10, for scheduling purposes).

We use filled region both in plan and elevation, so a half-half solution won't solve the problem.

We don't mind the area calculated parameters, which are just only a few.

---

Detail component families and filled regions are under the same category so parameters you added to filled regions will show for the families.  Nothing you can do about it except organize the parameters in a group and minimize the group from your properties palette.