Dynamic Parameter Name

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2018-08-29 10:48 AM
2018-08-29
10:48 AM
Is there a way to make Parameter names dynamic? So, the name changes depending on the value of some other variable?
eg.
If ProShape = "Round" then Parameter_Name ProWidth = "Profile Diameter" else Parameter_Name ProWidth = "Profile Width" endIf
Ling.
AC22-28 AUS 3110 | Help Those Help You - Add a Signature |
Self-taught, bend it till it breaks | Creating a Thread |
Win11 | i9 10850K | 64GB | RX6600 | Win11 | R5 2600 | 16GB | GTX1660 |
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2018-08-29 02:45 PM
2018-08-29
02:45 PM
If You wish to have parameters description dynamic, just use Interface script and
UI_LISTFIELD and the UI_LISTITEM commands.
The UI may look like the "old style" parameters list😉
Piotr
UI_LISTFIELD and the UI_LISTITEM commands.
The UI may look like the "old style" parameters list
Piotr

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2018-08-30 03:22 AM
2018-08-30
03:22 AM
A parameter (variable) in the parameter list can only have one name (description) - as far as I know.
You can manipulate it in the user interface as Piotr said.
When I need the choice of a rectangular or square shape I usually just use two different parameters (width and diameter) and hide the one not being used.
If you want them to be linked so one changes when the other is adjusted you can use GLOB_MODPAR_NAME to check when one is adjusted and set the value to the other accordingly.
Barry.
You can manipulate it in the user interface as Piotr said.
When I need the choice of a rectangular or square shape I usually just use two different parameters (width and diameter) and hide the one not being used.
If you want them to be linked so one changes when the other is adjusted you can use GLOB_MODPAR_NAME to check when one is adjusted and set the value to the other accordingly.
Barry.
One of the forum moderators.
Versions 6.5 to 27
i7-10700 @ 2.9Ghz, 32GB ram, GeForce RTX 2060 (6GB), Windows 10
Lenovo Thinkpad - i7-1270P 2.20 GHz, 32GB RAM, Nvidia T550, Windows 11
Versions 6.5 to 27
i7-10700 @ 2.9Ghz, 32GB ram, GeForce RTX 2060 (6GB), Windows 10
Lenovo Thinkpad - i7-1270P 2.20 GHz, 32GB RAM, Nvidia T550, Windows 11

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2018-08-30 03:25 AM
2018-08-30
03:25 AM
Was hoping there would be a way, as you can't set up a UI for a custom door leaf... >,<
Ling.
Ling.
AC22-28 AUS 3110 | Help Those Help You - Add a Signature |
Self-taught, bend it till it breaks | Creating a Thread |
Win11 | i9 10850K | 64GB | RX6600 | Win11 | R5 2600 | 16GB | GTX1660 |
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2018-09-01 06:13 PM
2018-09-01
06:13 PM
Use the UI commands I gave earlier...and conditionally display one or the other parameters...
But if there will be many of them...there might be a problem (maybe partly solved since I hit the wall of 1024 parameters in Door/Window objects), all depends how many ot the parameters need to be added.
BTW If You deal with custom components You can use the calling "by name" (of the real object that is on the list ) not the calling the component-template object with the name of the real object as a parameter. It gives some additonal possibilities - like override the called object material (via group commands), or calling the object other than the saved as a door leaf (or other)...You can condition the load of the other object and give the access to the say 4-5 surfaces (if the object is saved normally they will get the parameters).
Few thoughts...while I was thinking about tweaking the custom components...but the shortage of time did not let me put it into a working prototype.
Piotr
But if there will be many of them...there might be a problem (maybe partly solved since I hit the wall of 1024 parameters in Door/Window objects), all depends how many ot the parameters need to be added.
BTW If You deal with custom components You can use the calling "by name" (of the real object that is on the list ) not the calling the component-template object with the name of the real object as a parameter. It gives some additonal possibilities - like override the called object material (via group commands), or calling the object other than the saved as a door leaf (or other)...You can condition the load of the other object and give the access to the say 4-5 surfaces (if the object is saved normally they will get the parameters).
Few thoughts...while I was thinking about tweaking the custom components...but the shortage of time did not let me put it into a working prototype.
Piotr