How does one remove variables placed in a GDL macro by AC?

[Hubert Wagner]

Hello:

When I moved my GDL scripts to v8.1, I found many parameters had been quietly added by AC. These appear in blue text in the editor and fill up the parameter window.

I can't find a way to get rid of them. (When one is selected, the 'Delete' button is inactive).

Any ideas?

DW

[Anonymous]

Douglas wrote:
When I moved my GDL scripts to v8.1, I found many parameters had been quietly added by AC. These appear in blue text in the editor and fill up the parameter window.

I can't find a way to get rid of them. (When one is selected, the 'Delete' button is inactive).

Objects containing this "blue text" have been assigned a "subtype". This is to assure consistency between objects which are similar in nature. So for example, the variable gs_door_frame is used constantly on all doors rather than having the variable be gs_door_frame and door_frame in another door. It helps (I believe) developers of library parts, it assures continuity from one version to the next and makes it easier to create lists among other things.

Once an object has been created as a subtype, there is no way to remove those variables nor, as far as I'm concerned (don't mean that in a smart-ass way), would you want to do so.

woodster

[David Maudlin]

Douglas:

You cannot delete these parameters, but you can check the "X" button on the left so they do not show. If you are creating your own library, you may want to create your own subtype for consistancy and ease of contolling the parameters of multiple library parts.


Woody:

One reason for wanting to remove a parameter: not all the parameters of a subtype may be used in all the library parts assigned to a subtype. For example the Door subtype includes a parameter for leaf thickness (gs_leaf_thk), but this parameter would have no use for a door opening (like D Arch Opening), so seeing this parameter in the part's dialog box would be confusing. While this doesn't remove the parameter, it does allow the parameter to be hidden when appropriate.

HTH,
David

[Anonymous]

You know, David, I almost went back and reposted to mention the X button

Woody

[Hubert Wagner]

Thank you for your quick replies gentlemen.

Consistency across the library makes sense. I'd not thought of that as I use mainly my own doors and windows.

In future I will not create redundent parameters but rather use the appropriate AC parameter.

Have a good weekend: DW

[__archiben]

woodster wrote:
So for example, the variable gs_door_frame is used constantly on all doors rather than having the variable be gs_door_frame and door_frame in another door. It helps (I believe) developers of library parts, it assures continuity from one version to the next and makes it easier to create lists among other things.

it also ensures that you can change the same parameter from a variety of different objects in one go (should you wish) without affecting any of the objects' other parameters.

~/archiben

[David Maudlin]

~/archiben wrote:
it also ensures that you can change the same parameter from a variety of different objects in one go (should you wish) without affecting any of the objects' other parameters.

Ben:
Good point. It also enables parameter transfers when using the new feature in ArchiCAD 9 that allows you to transfer common parameter settings between parts.

David