Forum Replies Created
-
AuthorPosts
-
Joachim Sühlo
ParticipantI would also be very interested in the answer
GDL Object Developer
b-prisma
MAC OSx 10.14Joachim Sühlo
ParticipantMaybe the penFG and penPG are not initialzed or not declared as parameters.
Or fillPOly1, fillPOLY2, fillpoly3GDL Object Developer
b-prisma
MAC OSx 10.14Joachim Sühlo
ParticipantYes:
IF p_num > 0 THEN VALUES “str_bildwahl” stCustomPicFiles_with_prefixGDL Object Developer
b-prisma
MAC OSx 10.14Joachim Sühlo
ParticipantThe script part I use is:
! ———————————————————————- !
! ————— C u s t o m p i c t u r e f i l e r e q u e s t
! ———————————————————————- !IF GLOB_FEEDBACK_MODE = 0 THEN
dim stCustomPicFiles[]
bCustomPicFileExist = APPLICATION_QUERY (“LIBRARY_MANAGER”, “USER_IMAGE_FILES”, stCustomPicFiles)p_num = VARDIM1(stCustomPicFiles)
DIM stCustomPicFiles_with_prefix[]
si = 1
int_num_prefix = STRLEN(str_prefix)IF (str_prefix # ” ” AND str_prefix # “”) THEN
FOR i = 1 TO p_num
IF STRSUB(stCustomPicFiles[i], 1, int_num_prefix) = str_prefix THEN
stCustomPicFiles_with_prefix[si] = stCustomPicFiles[i]
si = si + 1
ENDIF
NEXT i
ELSE
stCustomPicFiles_with_prefix = stCustomPicFiles
ENDIFp_num = VARDIM1(stCustomPicFiles_with_prefix)
ENDIF
GDL Object Developer
b-prisma
MAC OSx 10.14Joachim Sühlo
ParticipantAnd yes, there are special boolen buttons as well, which look a bit different than the example before:
UI_PICT_PUSHCHECKBUTTON “myBool”, “myText”, “myPict”, 1, 0, 110, 100, 30GDL Object Developer
b-prisma
MAC OSx 10.14Joachim Sühlo
ParticipantThis is a boolean exampe with 1 button:
UI_INFIELD{3} “b_MVO_endgroesse”, 0, 0, 25 ,25,
6, Tree_MVO_3, 2, 1, 25, 25, 25, 25,
1, “”, 0,
2, “”, 1But I am not shure if this looks the same as a UI_Button.
The grafic file Tree_MVO_3 is embedded, if you use an external it must be “Tree_MVO_3” or similar.
This file has 2 grafics beside each other, one for the Value zero, the other for the value 1.GDL Object Developer
b-prisma
MAC OSx 10.14Joachim Sühlo
ParticipantDo you mean something like UI_Radiobutton?
GDL Object Developer
b-prisma
MAC OSx 10.14Joachim Sühlo
ParticipantI worked it out by calling an empty hole macro. Thanks.
GDL Object Developer
b-prisma
MAC OSx 10.14Joachim Sühlo
ParticipantA circular hole works for me with (in AC 23):
wallniche 2, 1, 2+16,
0,0,1, 1,
0, B/2, 979 + 16,
A/2,360,4079 + 16GDL Object Developer
b-prisma
MAC OSx 10.14Joachim Sühlo
ParticipantThank You, Péter, this works well!
GDL Object Developer
b-prisma
MAC OSx 10.14Joachim Sühlo
ParticipantThis works for me in Master Script:
name = “”
n = REQUEST (“Zone_relations”, “”, category_name, code, name, number)IF name = “Essen” THEN is = “11” ELSE is = “”
PARAMETERS is = isTEXT2 0, 0, name + is
GDL Object Developer
b-prisma
MAC OSx 10.14Joachim 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.14Joachim 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.14Joachim 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.14September 9, 2019 at 08:47 in reply to: How to pass all parameters with some exception to macro? #18156Joachim Sühlo
ParticipantIf you want to get a list of all parameters for the macro call, place the object to be called in the floor plan and save it as (dummy) object.
When you open this object, there should be the complete CALL statement with all parameters.GDL Object Developer
b-prisma
MAC OSx 10.14 -
AuthorPosts