Instance Parameter from a Window Family becomes Read Only when uploaded on a Project File

Instance Parameter from a Window Family becomes Read Only when uploaded on a Project File

coelho2319
Participant Participant
1,239 Views
10 Replies
Message 1 of 11

Instance Parameter from a Window Family becomes Read Only when uploaded on a Project File

coelho2319
Participant
Participant

I have a small program in Dynamo that creates vertical point grids in walls placed in a project file, according to their length and height values or level constraints, and then positions a circular-shaped Window Family that I created in every point. This Window Family currently has three subtypes that vary in size by having different radius parameters values. The program places the three subtypes randomly on the previously created grid. I'm currently trying to make a different window family whose size can be controlled through the Dynamo program with a flexible radius parameter for a smoother transition between the placed windows while working with attractors for instance. However, every time I attempt to create a new Window Family I end up with a Radius parameter that can neither be changed inside a project file nor through Dynamo since it became a read-only parameter.

 

Is there any way to avoid this or a more proper way to approach the situation?

 

Best of Regards,

RC

0 Likes
1,240 Views
10 Replies
Replies (10)
Message 2 of 11

ToanDN
Consultant
Consultant

@coelho2319 wrote:

I have a small program in Dynamo that creates vertical point grids in walls placed in a project file, according to their length and height values or level constraints, and then positions a circular-shaped Window Family that I created in every point. This Window Family currently has three subtypes that vary in size by having different radius parameters values. The program places the three subtypes randomly on the previously created grid. I'm currently trying to make a different window family whose size can be controlled through the Dynamo program with a flexible radius parameter for a smoother transition between the placed windows while working with attractors for instance. However, every time I attempt to create a new Window Family I end up with a Radius parameter that can neither be changed inside a project file nor through Dynamo since it became a read-only parameter.

 

1. This doesn't make sense.  Do you mean you are placing window instances or creating a new window type? 

2. Your title says Instance parameter but you use 3 family types, indicating Type parameter.  Type parameter must be edited via Type properties, not Instance properties.

 

Is there any way to avoid this or a more proper way to approach the situation?

 

Best of Regards,

RC


 

0 Likes
Message 3 of 11

RDAOU
Mentor
Mentor

@coelho2319 

 

From what you described my guess is that you are using the wrong node(s) to set value.

  • Either change the diameter/radius in the window family to Instance parameter
  • Or ...
    1. introduce an element.type node to work with type parameters
    2. Use a different set value node which sets type parameters

 

 

YOUTUBE | BIM | COMPUTATIONAL DESIGN | PARAMETRIC DESIGN | GENERATIVE DESIGN | VISUAL PROGRAMMING
If you find this reply helpful kindly hit the LIKE BUTTON and if applicable please ACCEPT AS SOLUTION


0 Likes
Message 4 of 11

coelho2319
Participant
Participant

First, I apologize for the late reply. What I meant to say was that I created a Window Family that has three types that vary in radius ( in this family the radius is a Type Parameter ). This family is being placed, as I mentioned before, in several points generated by a Dynamo program. However, I intend to have a more wide diversity of windows to be placed without having to create a new family type and manually change the radius. Therefore I attempted to create a new window family from scratch where I would manage to get the radius to be an Instance Parameter so that I could freely change it in the project file using dynamo. Nonetheless, this "radius" parameter always ends up being read-only, ( because it has type parameters on its formula ), hence I can't change it neither manually in the project file or the Dynamo Program.

0 Likes
Message 5 of 11

ToanDN
Consultant
Consultant

@coelho2319 wrote:

First, I apologize for the late reply. What I meant to say was that I created a Window Family that has three types that vary in radius ( in this family the radius is a Type Parameter ). This family is being placed, as I mentioned before, in several points generated by a Dynamo program. However, I intend to have a more wide diversity of windows to be placed without having to create a new family type and manually change the radius. Therefore I attempted to create a new window family from scratch where I would manage to get the radius to be an Instance Parameter so that I could freely change it in the project file using dynamo. Nonetheless, this "radius" parameter always ends up being read-only, ( because it has type parameters on its formula ), hence I can't change it neither manually in the project file or the Dynamo Program.


What is the formula?

0 Likes
Message 6 of 11

coelho2319
Participant
Participant

The existing element.type nodes in Dynamo do not serve the purpose I intend to achieve. From what I've found they mainly extract information from a given element type.

 

For the set value node I am currently using the Element.SetParameterByName. It works perfectly with other parameters, however with read-only parameters (that can't be edited in the project file) it doesn't.

0 Likes
Message 7 of 11

coelho2319
Participant
Participant

In the attached files are some previews of the formulas used in the window family. Here the "radius" parameter that I mentioned earlier is named "Outer_Radius".

0 Likes
Message 8 of 11

ToanDN
Consultant
Consultant

Outer Radius is still a Type parameter.  In fact, none of them are Instance Parameters except for Window Angle. 

 

ToanDN_0-1642454583200.png

 

 

0 Likes
Message 9 of 11

coelho2319
Participant
Participant

Yes, I'm aware of it. I made it "type parameter", before saving the last edit in that family file, since making it "instance" is useless as I cannot change it in the project file. 

0 Likes
Message 10 of 11

ToanDN
Consultant
Consultant

@coelho2319 wrote:

Yes, I'm aware of it. I made it "type parameter", before saving the last edit in that family file, since making it "instance" is useless as I cannot change it in the project file. 


Yeah it is confusing when you posted one thing and described another.  Can you share the Dynamo script then?

0 Likes
Message 11 of 11

coelho2319
Participant
Participant

Sure. Here is a preview.

0 Likes