We value your input!
Please participate in Archicad 28 Home Screen and Tooltips/Quick Tutorials survey

GDL
About building parametric objects with GDL.

UI_CUSTOM_POPUP_INFIELD{2} does not Update

Jochen Suehlo
Moderator

If I use UI_CUSTOM_POPUP_INFIELD{2}, whose values are changed dynamically, the selection of UI_CUSTOM_POPUP_INFIELD{2} in the user interface does not update.

Example:
Parameter 1 is changed, which changes the selection for parameter 2, whereby parameter 2 is to be displayed by UI_CUSTOM_POPUP_INFIELD{2}.
Now the value in the UI remains at the old value instead of switching to the only value actually available, or to the first of several.

Is there a way for UI_CUSTOM_POPUP_INFIELD{2} to update automatically?

Jochen Suehlo . AC12-27 . MAC OSX 14.4 . WIN11
GDL object creation: b-prisma.de
3 REPLIES 3
Peter Baksa
Graphisoft
Graphisoft

Hi,

 

UI_CUSTOM_POPUP_INFIELD{2}'s purpose is to work without setting values in parameter script.

Just guessing, maybe you have to do your parameter logic in the ui script. Or try different storeHiddenId setups.

 

 

Péter Baksa
Software Engineer, Library as a Platform
Graphisoft SE, Budapest
Jochen Suehlo
Moderator

Hi Peter,
Thank You for your answer. Yes, I am using this command, because I cannot work with VALUES.
The calculation is done in 3 subroutines in the Master-Script which are called from the UI Script.
The storeHiddenId only works with the Value 1 in my case.
My command looks the following:

			UI_CUSTOM_POPUP_INFIELD{2} str_sortiment_best[i][j],  in_x_2, dy, in_L_2, 24,
				1, 1, 1, "", 				! storeHiddenId, treeDepth, groupingMethod, selectedValDescription
				_sort_wahl

JoachimSuehlo_0-1707229020619.png

When I change value 1, the popup infield "2" shows "missing value" instead of the first value which is not missing.

 

Jochen Suehlo . AC12-27 . MAC OSX 14.4 . WIN11
GDL object creation: b-prisma.de
Peter Baksa
Graphisoft
Graphisoft

Hi,

yes, this is how it works, similar to UI_INFIELD. It stores the ID of the selection in str_sortiment_best.

Parameter values can only be changed in the parameter script. If the available choices are not known in the parameter script, nothing can be done.

You can show another string instead UNAVAILABLE VALUE in the closed state with selectedValDescription.

 

Péter Baksa
Software Engineer, Library as a Platform
Graphisoft SE, Budapest