Home › Forums › Problems and solutions in GDL › Informations from the environment › zone stamp: default property settings
- This topic has 6 replies, 2 voices, and was last updated 5 years, 5 months ago by
Péter Baksa.
-
AuthorPosts
-
-
November 6, 2019 at 19:40 #18351
Joachim Sühlo
ParticipantIn the German default zone stamp you can choose to show properties.
When you open the object and want to set a special property as default (in the GDL editor),
this is not possible.
The zone stamp macro uses the code:UI_CUSTOM_POPUP_LISTITEM itemID, UIGroup, _paramContentIDbyRow[iUI], 0, “” , “”, 1, 3, 1, _displayedProperty,
“”, “”, “”,Keine
,
parentProperties`When I use instead the following, I can add default values in the editor:
ui_custom_popup_infield “sIDRow1_50”,
50, 244, 222,20, ! X Position, Y Position, Width, Height
1, ! Store Hidden ID
3, ! Tree Depth
1, ! Grouping Method
_displayName, ! Created value description
_parentPropertiesIs there a way to change the code in the first example, to allow the definition of fdefault values in the GDL editor?
GDL Object Developer
b-prisma
MAC OSx 10.14 -
November 7, 2019 at 09:17 #18353
Péter Baksa
KeymasterI couldn’t get the second one to work either.
The parameter list in the GDL editor is not connected to anything in the UI script, it is only affected by the parameter script.
You can’t get the property GUIDs in the parameter script, that’s why the UI_CUSTOM_POPUP_LISTITEM and UI_CUSTOM_POPUP_INFIELD were created.Péter Baksa
Library Platform, Software Engineer
GRAPHISOFT SE -
November 7, 2019 at 09:19 #18354
Péter Baksa
KeymasterThe property GUIDs are project-dependent, a default value of the library part wouldn’t work in another plan.
Péter Baksa
Library Platform, Software Engineer
GRAPHISOFT SE -
November 7, 2019 at 09:47 #18355
Joachim Sühlo
Participantthe 2nd example had some Requests before. This code is from the gdl.graphisoft.com website.
In the example zone stamp both master and parameter script are empty.dim _parentProperties[]
n = REQUEST (“Properties_Of_Parent”, “”, _parentProperties)_displayName = “”
n = REQUEST (“Property_Name”, sIDRow1_50, _typeName, _groupName, _propertyName)
if _typeName # “” then _displayName = _typeName + ” : ”
if _groupName # “” then _displayName = _displayName + _groupName + ” : ”
_displayName = _displayName + _propertyName ! no need to check, always has a string valueui_custom_popup_infield “sIDRow1_50”,
50, 244, 222,20, ! X Position, Y Position, Width, Height
1, ! Store Hidden ID
3, ! Tree Depth
1, ! Grouping Method
_displayName, ! Created value description
_parentPropertiesGDL Object Developer
b-prisma
MAC OSx 10.14 -
November 7, 2019 at 09:58 #18356
Joachim Sühlo
ParticipantThe property GUIDs are project-dependent, a default value of the library part wouldn’t work in another plan.
Does this also applies to projects always created from the same Template file?
GDL Object Developer
b-prisma
MAC OSx 10.14 -
November 7, 2019 at 10:12 #18357
Joachim Sühlo
ParticipantDoes this also applies to projects always created from the same Template file?
I checked this both with a pln, saving under a neww name and a tpl saving under a new name:
both works, the GUIDs stay the same.GDL Object Developer
b-prisma
MAC OSx 10.14 -
November 7, 2019 at 10:35 #18358
Péter Baksa
KeymasterAs long as the properties aren’t deleted by the user in Options / Property Manager.
Péter Baksa
Library Platform, Software Engineer
GRAPHISOFT SE
-
-
AuthorPosts
- The forum ‘Informations from the environment’ is closed to new topics and replies.